This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/

Obsoleting "connect"

Previous message (by thread): Obsoleting "connect"
Next message (by thread): Obsoleting "connect"

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Havard Eidnes Havard.Eidnes at runit.sintef.no
Thu Sep 23 10:05:21 CEST 1993

> I tend to agree with you here but before we change the database config to
> make connect optional I guess we should get the okay from the chair who
> will be coordinating the new definitions for the objects. 

I agree.

> Also, we can take it a step further in that if the connect field is there
> it is LOCAL (something to add to the syntax checker ;-().

I was thinking of a multi-step phase-in of the new policy, and that this
would be the natural next step.  Or do we just jump into it with both feet
rigt away?

- Havard

Previous message (by thread): Obsoleting "connect"
Next message (by thread): Obsoleting "connect"

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]