From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
---|---|
To: | andreas(dot)percher(at)automedia(dot)de |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Columns out of range-error |
Date: | 2004-08-21 02:18:22 |
Message-ID: | 4126B0EE.2070900@opencloud.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Andreas Percher wrote:
> Sending a "begin" it gives us a SQL Error
> "Spaltenindex außerhalb des gültigen Bereichs"
> Which meens
> "The column index is out of range."
>
> --> postgresql.res.colrange:Spaltenindex außerhalb des gültigen Bereichs
>
> --> postgresql.res.colrange:The column index is out of range.
>
> This error message occur after 13-16 inserts, depending on the column
> count of each insert. Sending the inserts without the long data field
> "specialequipment", results in letting the error occur one insert later.
>
> In case of the Error, round about 600 columns (counted over all inserts)
> are waiting for its commitment.
Can you provide the full stack trace? I just dug through the driver and
the only place that this exception will be thrown is when querying a
ResultSet (either a ResultSet.getXXX() call, or from inspecting a
ResultSetMetaData). It seems strange that these methods would ever get
invoked if you're only doing updates..
-O
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2004-08-21 16:03:07 | Re: Columns out of range-error |
Previous Message | Oliver Jowett | 2004-08-20 23:10:04 | Re: Columns out of range-error |