> The SQL spec allows you to have a default schema that would apply to
> a_table automagically. IIRC, the default schema may be specified per
> session, if necessary.

And this is exactly the source of mess. We have default schema and
current (user) schema. Which one will have precedence in naming
resolution? I guess - current one. If a brainless user has created any
table with the same name as in default schema, support list will have
bad day guessing "where all data disappeared to".

SY, SD.