Thierry,
We had several issues with Access, and it is not a supported database. I notice that you only made changes to SQLEngine.SQLQuery. Does it means that the load() method of SQLEngine doesn't have the same problem? If it is true, I suspect there is a simpler way to fixes the problem. Your patch seems to be a little bit too complex. Thank for your contribution. Thomas -----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] >Sent: Friday, February 15, 2002 9:45 AM >To: [EMAIL PROTECTED] >Subject: [castor-dev] Patch/Modifications on Castor/JDO for Jdbc/Odbc compatibilty (Access) > >I found that Castor JDO / Engine > org.exolab.castor.jdo.engine classes > did for a current ResultSet object several time the > request to get a some column values (like for the identity columns) > that resulted in some databases (e.g.: Access through Jdbc/Odbc >Access driver) > do throw an Exception: No Data Found. > > I then corrected the problem in two classes for this problem > (package "org.exolab.castor.jdo.engine": SQLTypes and SQLEngine > classes > and forced to add another class CachedColumn to be able to cache > the current Column of a Row of a ResultSet for subsequent > get access on these column alreay in the cache.). > > I include here the diff for SQLTypes.java and SQLEngine.java >as well as the new class CachedColumn.java. > > > > Thank for this tool > Thierry BODHUIN > ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
