On Mar 2, 2011, at 1:11 PM, TShelver wrote: <snip>
> Heavy use is made of views, stored procedures, triggers, dynamic SQL, > against a very robust data model that so far has needed minimal change > across several complex implementations. > Some of the features are a data-driven policy engine (dynamic SQL allowing > multiple provisioning and reporting applications to access the logic that > determines who can get what, who should have what, or what can be given to > users with specific demographics). a scheduling and control application, > full audit / history of all actions including configuration and also user > access rights, and more. > > The solution has to integrate into multiple corporate applications for both > provisioning and access reporting purposes. It also has to be able suck > data from SIEM and other tools in the future, which is a huge challenge in > terms of data volumes. > <snip> > > I doubt that the Django ORM will work. So far, SQL Alchemy seems to be the > closest, the little reading I've done suggests that I could interact with > the backend via standard SQK, or stored procedures / table-valued functions. SQLAlchemy is sole reason we decided to choose TurboGears. Nothing else comes close and the amazing mailing list support from Michael Bayer made it an easy decision. If you are using stored procedures, triggers, views, or anything beyond basic tables and types, you will need to use SQLAlchemy. All the other HTTP-parsing and -routing and HTML-templating engines are effectively the same (or pluggable) with the competition frameworks. Cheers, M -- 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.
