Hi, I solved this problem, by doing this:
sqlalchemy.clear_mappers() I don't know why this solved the problem. Let me give you the gist of how I lead up to this problem: I wrote a custom query and selected a few columns out of a table. I then wanted to 'instantiatize' it so that i could reference the attributes as an object so I did that by calling the constructor of the sqlalchemy class that maps to the table. Now, I believe, since these classes were instantiated, sqlalchemy will try to force commit them at the end of the session. I hate this and don't know how to get rid of this feature. So basically, after reading the list of objects in, I do the updates and that's when I got blocked in mysql. I called sqlalchemy.clear_mappers(), and called session.clear() and it worked fine since then. Any ideas why it worked? Thnanks, Saureen. On Jun 30, 9:02 am, "Lee McFadden" <[EMAIL PROTECTED]> wrote: > Sam, > > If you could supply some code to show us what you're doing the list > may be able to help you more. At the moment any replies to your > thread will be pure guess work. > > Things that would be helpful to see: > > * Your custom query > * Surrounding controller code when running the query > > You should also post anything else that you might think is pertinent. :) > > Lee > -- > Lee McFadden > > blog:http://www.splee.co.uk > work:http://fireflisystems.com > skype: fireflisystems --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
