On retesting, it seems that the tables defined in SA declarative style are auto-created but the Elixir is not. So maybe I need another metadata2 bound to Elixir with something like model.metadata.create_all(bind=config['pylons.app_globals'].elixir_engine)
but it is not so obvious to me how to get elixir_engine working and then I will be mixing SA and Elixir... I see there was some discussion about this back in 2007 re. Default DB layer and Elixir vs. DB http://groups.google.com/group/turbogears/browse_thread/thread/5e8553a267223a0c/5cbb0247081ef4eb?lnk=gst&q=using+elixir#5cbb0247081ef4eb It seems a shame to me that Elixir lost out because to me it is much more intuitive. SA's "backref" for relations is ridiculous. A relation is by definition "bi-directional" and an RDBMS should handle relations easily. Sure SA is more powerful for enterprise apps where the DB has diverged from the business objects (and maybe wasn't so well designed in the first place!) but for a simple web app where the developer wants to "quickstart" with a new DB, I see nothing wrong with the ActiveRecord pattern. Anyway, I go now to look up Elixir session metadata engine etc. Perhasp my post should be re-titled "metadata.create_all() using Elixir". -- 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.
