On Thu, Feb 12, 2009 at 4:20 AM, Christoph Zwerschke <[email protected]> wrote: > > Lukasz Szybalski schrieb: >> sa_table def, python class, mapper seem like a natural approach. I'm >> not sure what declarative_base does for me that is different? >' please see http://www.sqlalchemy.org/docs/05/ormtutorial.html#creating-table-class-and-mapper-all-at-once-declaratively
> The "threefold path to enlightenment" you're mentioning has always > bothered people, because it's not so concise to write down and also > difficult to read. If you want to understand a database model object, > you have to read both its class and table definition which are in > different places in the model files. It fact it had bothered people so > much that various add-ons have been written, including "Elixir." > > That's why the declarative usage is now the standard way of using > SQLAlchemy, and I think it's good to make it also the standard in TG2. > You can still use the threefold way if you like it more. In fact I > noticed the 20min Wiki tutorial is still using it (but I think this > should be changed to not confuse new users). yes, I think there is a ticket for that. > > -- Christoph > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
