shday wrote: > Another tid bit. During development, reflection can be a PITA because > it can increase application startup time considerably. This can be > overcome, however, by pickling your reflected metadata and using that > (instead of reflecting every time). >
My current application reflects 5 different dbs (3 postgres, 1 mysql, 1 sql server) at each start, the main one has 104 tables and views. Of the others, two have more than 400 tables, and I reflect only the ones I use. It takes a few seconds to reflect them, yes. SqlAlchemy's autoloading has served me well since 2006. I believe DDL belongs to SQL, and I think python code is not meant to be generated. I never defined tables in python, if not for replicating some bugs I found a long time ago. -- This e-mail (and any attachment(s)) is strictly confidential and for use only by intended recipient(s). Any use, distribution, reproduction or disclosure by any other person is strictly prohibited. The content of this e-mail does not constitute a commitment by the Company except where provided for in a written agreement between this e-mail addressee and the Company. If you are not an intended recipient(s), please notify the sender promptly and destroy this message and its attachments without reading or saving it in any manner. Any non authorized use of the content of this message constitutes a violation of the obligation to abstain from learning of the correspondence among other subjects, except for more serious offence, and exposes the person responsible to the relevant consequences. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
