> Is reflection under sqlalchemy a good idea? Discuss -- not too
> heatedly :)
I'm having an app with 63 tables and 43 views - all reflected at startup. It's
bit of a pain to do the views, because they don't have a primary key, so you
have to specify that.
Other than that, it works fine. The advantage of reflecting at startup is that
you don't have to alter code when you add a field (non critical field that
is) somewhere.
As others mentioned, the startup time goes up a lot. My app currently takes
about 20 seconds to start. However you can work around that.
I'm using a nginx load balancer in front of several instances, so when I reset
the system for an upgrade or bugfix, I reset the instances one at a time. The
user never sees the downtime, because the load balancers reroutes traffic to
the functional instances. All it does is make it a bit slower during a
restart.
Uwe
--
Open Source Solutions 4U, LLC 1618 Kelly St
Phone: +1 707 568 3056 Santa Rosa, CA 95401
Cell: +1 650 302 2405 United States
Fax: +1 707 568 6416
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
