Subject | Re: [firebird-support] Re: Stored procedure |
---|---|
Author | Robert martin |
Post date | 2005-03-03T20:34:55Z |
Thanks Helen
I spent hours trying to work out why my Stored Procedure parameters
worked differently to documentation. I have been using a tool we made
here for managing our databases. Its a general purpose tool so I have
upgraded it to detect stored procedures and use the more appropriate
ib_DSQL component.
My stored procedure now work like a charm :) I just wish I had asked
earlier !
Rob Martin
Software Engineer
phone +64 03 377 0495
fax +64 03 377 0496
web www.chreos.com
Wild Software Ltd
Helen Borrie wrote:
I spent hours trying to work out why my Stored Procedure parameters
worked differently to documentation. I have been using a tool we made
here for managing our databases. Its a general purpose tool so I have
upgraded it to detect stored procedures and use the more appropriate
ib_DSQL component.
My stored procedure now work like a charm :) I just wish I had asked
earlier !
Rob Martin
Software Engineer
phone +64 03 377 0495
fax +64 03 377 0496
web www.chreos.com
Wild Software Ltd
Helen Borrie wrote:
>At 04:59 PM 3/03/2005 +1300, you wrote:[Non-text portions of this message have been removed]
>
>
>
>>Hi
>>
>>I get an 'Unsuported column type: 0' error whenever I do this.
>>
>>
>>I have just discovered it is due to my component set, I am using an
>>IBOQuery to run this.
>>
>>
>
>Aha!! This is because IBOQuery parser thinks a colon-ised fieldname is a
>parameter and you haven't told it otherwise. That's a trap with using
>IBOQuery (which is designed for scrollable SELECT queries) to perform
>DDL. Use an ib_dsql, and make sure you set the property ParamCheck to False.
>
>(You might also achieve the same thing by setting this property False on an
>IBOQuery...raise further questions on the IBO support list....)
>
>./heLen
>
>
>
>
>
>Yahoo! Groups Links
>
>
>
>
>
>
>
>
>
>