On May 20, 10:13 am, "Rick Morrison" <[EMAIL PROTECTED]> wrote:
> > The SQL works in our SQL analyzer with or without the named parameter
> > and with the semicolon. We tried it the way you mentioned too, using
> > positional parameters, and got the same error. I apologize for
> > forgetting to mention that in my first post.
>
> Then perhaps you're not connected to the correct database, or it's a
> permissions issue? The way you're using the DB connection directly,
> SQLAlchemy is not issuing any SQL of it's own: it's a straight pass-through.
>
I don't think it's a permissions thing...see below...
> Positional parameters work with pymssql, so I assume you're using pyodbc,
> correct? I haven't tried calling a stored procedure using pyodbc, anybody on
> the list have that working?
I think we're using pymssql from a Linux box. Is there a way to tell
which Python module SQLAlchemy is using? We tried running it with
straight pymssql instead and it works in there:
<code>
import pymssql
db =
pymssql.connect(host="ntsql.ourSite.com",user="user",password="pw",database="ourDB")
cur = db.cursor()
cur.execute("execute sp_EDEN_Vendors @query='gra%';")
print cur.fetchall()
</code>
>
> > Any other ideas? I'll look into the OUT parameter that Bayer mentions
> > in his post.
>
> Well if IN parameters don't work, OUT parameters probably aren't going to
> work either. If you're using pyodbc, I would try bringing the issue up on
> the pyodbc list. You're pretty much using the DB-API cursor directly, so
> it's not interference from SQLA.....
Crumb. Thanks.
Mike
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
