Namespace is very interesting, and it totally slipped my mind. Although, Namespace seems a little ambiguous to me. this is a container for objects defined in the schema.py module and all extend SchemaItem.
Im going to start with Schema but if anyone else sees a compelling reason to go with Namespace, ive no problem switching. Qvx wrote: > I like both Schema and Namespace. If you ever need a real schema you could > call it DbSchema or DatabaseSchema. But then you would have similarly > named > things with different meening. Considering what I just said, I would vote: > > +1 Namespace - if I understood correctly what you were looking for in the > first place > +0.5 Schema - I like the name very much but there are other things named > Schema > > As for kw param, I would call it the same as the object it expects. This > could be the reason alone to choose Namespace over Schema or to go the > other > way and call param dbschema and someday have DbSchema if needed. > > On 4/11/06, Michael Bayer <[EMAIL PROTECTED]> wrote: >> >> >> >> Schema (conflicts with "schema" parameter, though that could just >> change >> to "schemaname") >> >> VirtualSchema (sounds goofy) >> Domain (conflicts with "set of all permitted atomic values" def) >> SQLDomain (ditto) >> Model (conflicts with the application's model) >> SQLModel (sounds weird) >> RelationalModel (reaching) >> TableSpace (oracle folks may dislike) >> >> the changes afoot are actually big enough that a switch of >> "schema='foo'" >> to "schemaname='foo'" is not the end of the world. Hold off on the >> Oreilly book press please (what animal would a SQLAlchemy be anyway ?) ! >> >> possible types of Schema: >> >> Schema(name) - a place to put your tables. no engines are in use, >> explicit Connections must be used to do things. >> >> BoundSchema(name, engine_or_url) - a place to put your tables, that can >> bind to an engine. SQL operations derived from SchemaItems bound to >> this >> Schema will be automatically bound to the underlying Engine if not >> overridden. >> >> DynamicSchema(name, threadlocal=True) - a place to put your tables, that >> binds to an engine, that has a connect() method that uses a particular >> engine on a thread-local basis >> >> >> >> >> >> >> >> >> >> ------------------------------------------------------- >> 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 >> > ------------------------------------------------------- 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
