Re: cx_Oracle callproc output parameters

2005-11-09 Thread Lao Tzu
Thanks! On 11/9/05, Gerhard Häring <[EMAIL PROTECTED]> wrote: > infidel wrote: > > I have a stored procedure that has a single output parameter. Why do I > > have to pass it a string big enough to hold the value it is to receive? > > Why can't I pass an empty string or None? > > [...] > > Am I mi

Re: cx_Oracle callproc output parameters

2005-11-09 Thread Diez B. Roggisch
Gerhard Häring wrote: > You have to use variable objects to the callproc() that will hold the > output values. This is an example using three VARCHAR output parameters. Oh boy, one never stops learning... I still thing a single in-out-value is crying for a function - but in case of several parame

Re: cx_Oracle callproc output parameters

2005-11-09 Thread Gerhard Häring
infidel wrote: > I have a stored procedure that has a single output parameter. Why do I > have to pass it a string big enough to hold the value it is to receive? > Why can't I pass an empty string or None? > [...] > Am I missing something obvious here? You have to use variable objects to the call

Re: cx_Oracle callproc output parameters

2005-11-09 Thread Diez B. Roggisch
infidel wrote: > I have a stored procedure that has a single output parameter. Why do I > have to pass it a string big enough to hold the value it is to receive? > Why can't I pass an empty string or None? > > import cx_Oracle as oracle connection = oracle.connect('usr/[EMAIL PROTECTED]

cx_Oracle callproc output parameters

2005-11-08 Thread infidel
I have a stored procedure that has a single output parameter. Why do I have to pass it a string big enough to hold the value it is to receive? Why can't I pass an empty string or None? >>> import cx_Oracle as oracle >>> connection = oracle.connect('usr/[EMAIL PROTECTED]') >>> cursor = connection