Steve Krueger has asked an interesting question: What happens to
database handles when DSQL executes a "drop database".

The root of the problem is that unless a transmission layer parses and
tracks the SQL, it won't know that the database has been dropped. ISQL,
in specific, seems to just abandon the database handle, leaving it
dangling as a memory leak.

A more clever implementation of "drop database" would have been to mark
the database for deletion when detached. We may want to go that way if
we can find a way to handle the backwards compatibility problems.

Does anyone have any other ideas?

--

Jim Starkey
Netfrastructure, Inc.
978 526-1376