its essentially a "framework" feature, you have a certain idea about how a fake "schema" might be implemented for databases that dont explcitly support schemas, such as through table name prefixes or modified sqlite filenames. both of which are entirely reasonable, for an application that chooses to do it that way. but lots of other applications would want no such thing. its not SA's place to make decisions like that, since SA is a library and not a framework. Every function name, keyword and argument name needs to do as much exactly what it says it does, and nothing more or less...since having surprise behaviors and ambiguity of function creates confusion.
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
