Sqlalchemy almist certainly implements transactions. The point is that insert is bad for bulk loading data. (I presume you are bulk loading because you want to use transactions for batch processing)
Correctly and quickly loading data is strongly depending upon the DB. E.g. For PostgreSQL you can achieve a magnitude of speedup by using COPY FROM STDIN; But the kinds hacks are out of scope for sqlalchemy. Andreas -- Urspr�ngl. Mitteil. -- Betreff: [sqlalchemy] Insert through ORM performance (was: Performance question) Von: "Gaetan de Menten" <[EMAIL PROTECTED]> Datum: 19.07.2007 08:15 [in response to a batch-insert-is-slow complaint on the Elixir list] On 7/19/07, AndCycle <[EMAIL PROTECTED]> wrote: > > I don't think db define is the major problem, > it could be sqlalchemy's problem, > because currently it haven't implement real transaction command in > most db implementation, > all the do_begin define is bypass, so you won't get any efficient > batch db access right now. I'm not sure how much of this is true. I'd like to hear any comment about this by people more knowledgeable than me on that topic. -- Ga�tan de Menten http://openhex.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---