> In my mind the point of the "database" concept is to provide a domain
> within which custom datatypes and functions are available. Schemas
> will control the visibility of tables, but SQL92 hasn't thought about
> controlling visibility of datatypes or functions. So I think we will
> still want "database" = "span of applicability of system catalogs"
> and multiple databases allowed per installation, even though there may
> be schemas subdividing the database(s).
Yes, and people wanting only one database like in Oracle will simply only
create one database. The only issue I can think of is that they can have
some "default database" other than the current dbname=username, so
they don't need to worry about it.
Andreas