Mostly I'm trying to avoid global state like metadata. The Tables themselves are global, but I feel like the metatdata maybe shouldn't be? I'm not a SQL alchemy expert so maybe what I'm trying to do is crazy and the answer is don't do that. Mostly I'm trying to figure out what patterns are best for testable apps written with SQL alchemy.
> On Sep 22, 2013, at 11:41 PM, Michael Bayer <[email protected]> wrote: > > > this is one of those, "why do you want to do that" kinds of questions. You > probably have a tometadata() use case of some kind, see > http://docs.sqlalchemy.org/en/rel_0_8/core/metadata.html?highlight=tometadata#sqlalchemy.schema.Table.tometadata > > > >> On Sep 22, 2013, at 10:30 PM, Donald Stufft <[email protected]> wrote: >> >> So all of the examples i've seen either explicitly pass in a schema or do it >> implicitly via the declartive_base. My question is can I create a table and >> associate it with a metadata at a later point? >> >> -- >> You received this message because you are subscribed to the Google Groups >> "sqlalchemy" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/sqlalchemy. >> For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/groups/opt_out.
