Jacques Desmazieres wrote:
I have investigated deeper, and actually the probleme comes from a
middleware layer we had to develop in order to be able to use the Odbc
bridge with OJB (this driver is no more supported since 1.0.1 as OJB does
not respect the constraint of accessing the result set columns in the same
order as in the query).
This rings a bell. Please have a look at OJB-26 in JIRA and confirm that
what you are explaining is the same issue:
http://issues.apache.org/jira/browse/OJB-26
So, the problem is in our code (even if this code had been to be implemented
because of an OJB restriction / regression)
I would like to fix this in OJB if possible, do you know why this has
changed or what causes the problem?
Am I right when I read this as eg:
SELECT a,b,c FROM table
and:
rs.get(<column different than a>)
Where as it would work with JDBC-ODBC bridge if OJB did:
rs.get(<a>) before rs.get(<b>) before rs.get(<c>)
in that exact order?
Regards,
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
