It incorrectly implies that the contents are associated with a database schema, which is bad enough. But even more confusingly, it's possible for the thing to hold Tables and other database objects that really *are* in a different database schema (i.e.have object.table_schema set).
TableSpace is less confusing (at least for non-Oracle DBAs), but still suffers from that same terminology overloading problem.
Basically, those two names are already taken. Sure, they're good (that's why they're already taken), but taken. This new construct is more or less a combination of a namespace and a psuedo schema.
So,
+1 SchemaSpace / SchemaContainer / SchemaObjects / SchemaWhatever
Rick
On 4/12/06, Michael Bayer <[EMAIL PROTECTED]> wrote:
OK so we have:
Schema
TableSpace
TableSchema
NameSpace
SchemaSpace
Room
AppSchema
im still partial to "Schema" or maybe TableSpace. Keep in mind that this
thing will probably have functions like:
schema.tables
schema.create_all()
schema.drop_all()
schema.constraints
schema.indexes
etc.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Sqlalchemy-users mailing list
Sqlalchemy-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
