On Mar 22, 2010, at 4:06 PM, Kevin Wormington wrote:
>
>
> Michael Bayer wrote:
>> On Mar 22, 2010, at 3:48 PM, Kevin Wormington wrote:
>>> That's getting closer. Now if I could just figure out how to get it to use
>>> the parameters that I'm actually passing in engine.execute. It appears
>>> ibm_db_sa botches the sql (to "CALL BILLING.subscriber_balance()") if use
>>> the commented out cursor.callproc(statement, parameters).
>> well you're right there so figure out what is different about "parameters"
>> versus your tuple there. a good candidate is, "parameters" is probably a
>> list, not a tuple.
>
> parameters is an empty list coming into ProcedureProxy.cursor_execute.
> Somehow the parameters aren't making it from the engine execute to
> cursor_execute - which probably has to do with my modification of the
> @compile decorator but my Python skills are not that great yet to know what
> to change.
wheres the parameters here ?
res = engine.execute(procedure("BILLING.subscriber_balance", subid, balance))
should be engine.execute(procedure(...), {'param1':p1, 'param2':p2})
>
> cursor.execute accepts either a list or tuple
>
> Thanks,
>
> Kevin
>
> --
> You received this message because you are subscribed to the Google Groups
> "sqlalchemy" 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/sqlalchemy?hl=en.
>
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" 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/sqlalchemy?hl=en.
