On Apr 16, 2007, at 5:54 PM, George Sakkis wrote:
> > Is there any way I can force a COMMIT within an exposed method ? I am > using SqlAlchemy with PostgreSQL and I am creating a few records that > I need to use for subsequent SELECTs within the same method. Although > I do flush() them and get their assigned IDs, subsequent explicit > SELECTs (using SA's select(), not the data mappers) fail to see the > changes. How are you obtaining the engine when you use SA's select? You should use the same connection the transaction is using so you see its changes, check out [1] > > Alternatively, is there an easy way to turn off the transaction > altogether for a specific method ? The workaround shown in [1] looks > messy and error prone. Not that I'm aware of. Alberto [1] http://tinyurl.com/35uter --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
