It is the server that determines the datatype, not me on the client.
I might be able to do an override and type cast, ignoring what the server
recommended but the level of logic and checking would create slower
performance, more complex code, etc.

What I'd rather see is you give each of those parameters unique names and
handle them accordingly.

Jason

> -----Original Message-----
> From: Carlos H. Cantu [mailto:listas@...]
> Sent: Sunday, March 13, 2005 6:20 AM
> To: Jason Wharton
> Subject: Re: [IBO] TIBOQuery 4.5Ah parameter bug?
>
> Jason,
>
> I don't know if you are talking about this, but:
>
> ... where ((:tabela = '*') or (:tabela = table.fieldA)) ...
>
> ps: fieldA is varchar(10)
>
> In this situation, IBO 4.5Ai creates 2 params with name tabela, one as
> char(1) and other as varchar(10). I think it should create just one
> parameter, as varchar(10).
>
> []s
> Cantu
> http://www.warmboot.com.br
> FireBase - http://www.FireBase.com.br
>
>
> JW> I found and fixed a parameter parsing problem for the
> next release and I
> JW> wondered if I could get a detail of this problem again so
> I can see if it is
> JW> resolved as well.
>
> JW> Jason Wharton
>