Re: Columns out of range-error
От | Dave Cramer |
---|---|
Тема | Re: Columns out of range-error |
Дата | |
Msg-id | 1093104187.20387.84.camel@localhost.localdomain обсуждение исходный текст |
Ответ на | Re: Columns out of range-error (Oliver Jowett <oliver@opencloud.com>) |
Ответы |
Re: Columns out of range-error
|
Список | pgsql-jdbc |
Oliver, This should throw an error if you try to setXXX(n,obj) if n is greater than the number of parameters you have? dave On Fri, 2004-08-20 at 22:18, Oliver Jowett wrote: > 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 > > ---------------------------(end of broadcast)--------------------------- > TIP 3: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly > -- Dave Cramer 519 939 0336 ICQ # 14675561 www.postgresintl.com
В списке pgsql-jdbc по дате отправления: