Its currently possible to have multiple databases pointing to the same catalog / data. DROPping any one of them without the KEEP CONTENTS clause will zap the data.

Suggestion (since I'm guessing the reason for allowing multiple databases to point to the same data is to allow different privileges to be set) - prevent the data being zapped until only one database points to it.

Roy Lambert

Roy,

<< Its currently possible to have multiple databases pointing to the same
catalog / data. DROPping any one of them without the KEEP CONTENTS clause
will zap the data.

Suggestion (since I'm guessing the reason for allowing multiple databases
to point to the same data is to allow different privileges to be set) -
prevent the data being zapped until only one database points to it. >>

We can't do so without putting in a link between the configuration and the
database catalog, and that would prevent you from hooking up any database to
any configuration by simply issuing a CREATE DATABASE statement.  It would
also prevent you from copying the contents of a database around using the
file system (provided that you know what you're doing and copy everything).

So, the definite answer on this one is "no can do".

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


It took me a few moments to sus that. I'd forgotten you can have multiple configuration files - sorry.

Roy Lambert