> 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 Yes, actually Kevin is working with me, and we worked together to fix this issue.
> > > 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? that would be great > Am I right when I read this as eg: > SELECT a,b,c FROM table > > and: > rs.get(<column different than a>) Yes > 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? Yes that's It. I did not investegated to see what change has generated the problem (too many classes involved in that problem changed between 1.0RC5 and 1.0.1. But the problem comes from the fact that PK and class name are treated separatly from other columns. If I remember well the problems occurs due to PK materialization Jacques --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
