Actually let me clarify - The Oracle Thin driver enforces the column order
on the getXXX. The sun jdbc:odbc driver (1.1) did not.
JV wrote in message ...
>We switched drivers and now it works. Thanks for all of the help.
>C. Ferguson wrote in message <38193326.3D6D9D0C_at_rationalconcepts.com>...
>>
>>I agree with Lee. I use a type 4 driver and retrieve columns in random
>order and get the
>>expected result with no problems. Since you are writing java and I assume
>you are using
>>Oracle, try using Oracle's jdbc driver.
>>cindy
>>
>>Lee Fesperman wrote:
>>
>>> JV wrote:
>>> >
>>> > We are not sure if this is the correct behavior for a result set.
>>>
>> -------------------------------------------------------------------------
-
>--
>>> > --------
>>> >
>>> > It seems that if the rs.getXXX( “whatever” ) are not in the same order
>as
>>> > the columns in the select statement it won’t work. After experimenting
>it
>>> > seems that once you have retrieved the value from a specific column,
>you can
>>> > ’t go backwards. It behaves the same way if we use column index
>instead of
>>> > column name on the getXXXX. If the columns are accessed in order,
>>> > everything works.
>>> >
>>> > Are we missing something or do the getXXXs need to be in the same
order
>as
>>> > the columns in order to retreive data out of the result set?
>>>
>>> This depends on the JDBC driver. Some drivers require that you 'get'
>columns in order.
>>> I believe this is the case with the JDBC/ODBC driver.
>>>
>>> --
>>> Lee Fesperman, FFE Software, Inc. (http://www.firstsql.com)
>>
>
>
Received on Fri Oct 29 1999 - 11:11:37 CDT
