Re: bug in DROP TABLESPACE

Christopher Kings-Lynne wrote:

>>
>
> It seems to me that we have mixed up two concepts:  the tablespaces 
> that a database is IN and the default tablespaces for any schemas 
> created in that tablespace.  This will probably cause trouble further 
> down the track :(


As long as we interpret schema and database tablespace just as default 
for future object creation, hopefully not. This leaves moving objects 
from one tablespace to another up to us tool suppliers, which seems 
reasonable.

Regards,
Andreas