"" is not null, so if sqlind was -1 this is a serious bug. Looking at the
FBStringField setString code, I don't see how this can happen, however.

david jencks

On 2002.04.05 10:33:19 -0500 Ken Richard wrote:
> I have just experienced this problem in a different way. I have a
> CallableStatement that was being called with stmt.setString(n,"") that
> was failing with the same exception. I did not set another value for
> the field prior to setting the empty string.
>
> I tracked it back in the code to GDS_Impl.java function isSQLDataOK
> method. It appears that the sqlind was set to -1 for the blank field
> but the sqldata was not null which caused the GDSException to be thrown.
>
> I was not able to recreate the problem with a simple example. I created
> a small program that uses 3 fields to try to recreate the error and it
> worked fine - even though my stored procedure (over 20 columns) was
> failing.
>
> -Ken
>
> -----Original Message-----
> From: rrokytskyy [mailto:rrokytskyy@...]
> Sent: Thursday, April 04, 2002 9:32 AM
> To: Firebird-Java@yahoogroups.com
> Subject: [Firebird-Java] Re: Incorrect values within SQLDA structure
>
>
> > I can send you my insert statement and my table definition, if you
> > want.
>
> Yes, please. I tried all setXXX methods you described, but it works
> fine for me. BTW, what version of database server do you use?
>
> Thanks!
> Roman Rokytskyy
>
>
>
>
>
> To unsubscribe from this group, send an email to:
> Firebird-Java-unsubscribe@yahoogroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
>
>