Are you calling these stored procedures directly with executesql(), or are they called by triggers or db views?
Immediately, I can imagine an issue occuring if the SP changes a value which is in an open web2py table connection (cache), so I'd be interested to know more about context, if you are commiting your tables (e.g. flushing any cache) before executsql( your_sp ). There may be other things involved, hard to say... On Tue, Jul 7, 2009 at 2:58 PM, ae <[email protected]> wrote: > > I use stored procedures for everything in my web2py application. > > All of a sudden, I'm having a strange issue with certain stored > procedures. > > It seems to be stored procedures that call other stored procedures. > > I've worked around the issue to some degree. > > I am not able to replicate this through the regular mysql client or by > running them through small python scripts (those both work ok). > > Any thoughts? > > --ae > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
