Hallo there! I've began exploring TG2.1 today after years of 1.x, and I like it.
It would be nice to start writing new modules for an existing business application, currently running under TG1.1. The current app has been in production since 2007, and porting the whole baby is unthinkable. Besides, I'm quite satisfied by its stability. Basically, I plan to share the DB, complete with authentication+cookie/ authorization, and little else. They would appear to the user as a single program, probably responding from 2 different ports. Every one of the 190 table/views is reflected, and I want it to stay that way. So instead of calling metadata.create_all() and metadata.drop_all(), I suppose I should execute a schema.sql, then autoload it inside init_model(), but I have a few issues with the testing machinery... I've already done the same for TG1.0, and then rewrote it for TG1.1, but my solution was voodooish and not pretty. Actually, it called TRUNCATE on all the tables, instead of DROP, thus creating the schema only once. I could keep the auth tables declarative like they are in the quickstart, but dropping them would not be possible due to the foreign keys linking them to the rest of the schema. I need to test with Postgres because of the triggers and the vendor- specific stuff. So I ask you: are your tg_user/tg_group/etc. reflected? What did you put in model.init_model(), schema.setup_schema(), tests.setup_db(), tests.teardown_db() ? I'd like to start with the right foot this time :-) Thanks a lot. -- 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.
