On Jul 18, 2008, at 5:43 AM, Ryan Tracey wrote:
> > Just a note on something I picked up concerning stored procedures and > MySQL. There's a thread (which I seem unable to locate now) which > ended with the suggestion that to get SPs working with SA and MySQL > one should edit databases/mysql.py and add the CALL keyword to the > regex which handles SELECTs, etc. > > SQLAlchemy-0.5.0beta1-py2.5.egg/sqlalchemy/databases/mysql.py > Diff: > 224c224 > < r'\s*(?:SELECT|SHOW|DESCRIBE|XA RECOVER)', > --- >> r'\s*(?:SELECT|SHOW|DESCRIBE|XA RECOVER|CALL)', > > The suggested patch works (for the way that I am using SPs) but has > not been applied to the main SA branch -- I have had to apply the > patch to a number of SA versions which have come out since the patch > was originally suggested. Is this an oversight or is there a reason > why the patch has not been applied. Just don't want to be shooting > myself in the foot with a patch that solves one problem and introduces > another. > this is already in 0.5beta2, trunk, and the 0.4 branch, back when it was suggested. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
