a
MySQL Stored Procedure.
Thanks in advance.
Stephen Ray
--
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sqlalchemy+unsubscr...@googlegroups.com.
To post
and then manipulate the cursor directly.
On Apr 18, 2013, at 9:18 AM, Stephen Ray stephen...@gmail.comjavascript:
wrote:
My environment is Python 3.2, SQLAlchemy 0.8, MySQL 5.5, and using
MySQL-connector 1.0.9.
I have a stored procedure that takes two input parameters (both integers)
and returns
.
Thanks for your help!
Steve R
On Thursday, April 18, 2013 1:09:39 PM UTC-4, Michael Bayer wrote:
yeah I've no idea, would need to get it working with raw cursor first to
even know how this should be treated.
On Apr 18, 2013, at 10:43 AM, Stephen Ray stephen...@gmail.comjavascript
My envirionment is SQLAlchemy 0.7.9, pyodbc 3.0.2, Python 3.2, and SQL
Server 2008 R2 running on Windows 7
I have the following Python (details of the connection url removed - the
connection to the db succeeds):
from sqlalchemy import create_engine, MetaData, Table
engine =
Michael Bayer wrote:
ok, dont change anything in turbogears yet. i think i have fixed the
problem, please try out rev 2133. ticket #387 explains the issue.
This issue seems very similar to one I found using the MySQL Zope
database adapter. The symptom was the same (MySQL has gone away), and