Subject | Re: PreparedStatements |
---|---|
Author | Nick Sydenham |
Post date | 2004-04-08T14:25:22Z |
OK, my fault, in the setXXX methods my index was as the fields
appeared in the table and not how they're defined in the SQL statement.
Can anyone explain what the following cryptic error means:
org.firebirdsql.jdbc.FBSQLException: GDS Exception. 335544794.
operation was cancelled
at
org.firebirdsql.jdbc.AbstractPreparedStatement.internalExecute(AbstractPreparedStatement.java:445)
at
org.firebirdsql.jdbc.AbstractPreparedStatement.executeUpdate(AbstractPreparedStatement.java:147)
Ta,
Nick
--- In Firebird-Java@yahoogroups.com, "Nick Sydenham" <nsydenham@y...>
wrote:
appeared in the table and not how they're defined in the SQL statement.
Can anyone explain what the following cryptic error means:
org.firebirdsql.jdbc.FBSQLException: GDS Exception. 335544794.
operation was cancelled
at
org.firebirdsql.jdbc.AbstractPreparedStatement.internalExecute(AbstractPreparedStatement.java:445)
at
org.firebirdsql.jdbc.AbstractPreparedStatement.executeUpdate(AbstractPreparedStatement.java:147)
Ta,
Nick
--- In Firebird-Java@yahoogroups.com, "Nick Sydenham" <nsydenham@y...>
wrote:
> --- In Firebird-Java@yahoogroups.com, "Roman Rokytskyy"specified by
> <rrokytskyy@a...> wrote:
> > > ps.setDate(4, parseDate(val));
> > >
> > > where parseDate returns a java.sql.Date with the hours, minutes,
> > > seconds and milliseconds set to 0.
> > >
> > > I am assuming that with a PS of 'insert into table (f1, f2, f4, f3)
> > > values (?, ?, ?, ?)' that the types are read in the order
> > > the SQL and not the order in which they are specified on the table.
> >
> > Correct, it uses order from the statement.
> >
> > > So fields 1, 2 and 4 are varchars, field 3 is a date on the table
> > > defintion. So PS.setDate(4, date) is still correct in theory.
> >
> > Yes. Can you please provide a test case - Java class that creates
> > appropriate table, populates it, and reproduces an error?
> >
> > Thanks!
> > Roman
>
> A test case works fine. It might have something to do with the fact
> that I've got 102 input parameters (noddy DB so design is limited
> :-)). I'll investigate further.