On Wed, 2010-07-07 at 23:40 +0530, Krishnakant Mane wrote: > I will be interested to know if using ORM for a large scale data > operation is the right approach when it comes to scalability. > Has SQLAlchemy been put to test ever for a select query which involves > getting thousands of records and specially when joins are involved?
Mere thousands? No problem. I have an application that regularly select ~22,000 objects involving multiple joins (some lazy, some not). > I have a financial software which needs such a system. > There will be lot of joins and will involve lot of complex queries. > If not then should I use the layer directly below the ORM? There are cases where straight DBAPI is faster - and you can use that in those cases. But generally [in my experience] SQLalchemy's performance penalty is quite low. I'd say that if you application is complex is all the *more* reason to use an ORM - as it automates much of the plumbing and is very well tested. -- Adam Tauno Williams <[email protected]> LPIC-1, Novell CLA <http://www.whitemiceconsulting.com> OpenGroupware, Cyrus IMAPd, Postfix, OpenLDAP, Samba -- You received this message because you are subscribed to the Google Groups "sqlalchemy" 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/sqlalchemy?hl=en.
