A better solution (IMO) would be to have the JDBC classes extend abstract classes that actually implement the JDBC interfaces and just thrown OperationNotSupportedException for all methods. Then the subclasses can selectively override the methods they support. This will make it work on both JDBC 3 and 4. Then gradually implement the additional methods.
On 5/27/07, Fabian Groffen Fabian.Groffen@cwi.nl wrote:
On 27-05-2007 09:32:04 +0200, Ramon Nogueira wrote:
OK, actually going to use CVS, since that's probably easier. Just a point about compiling the Java client (which as far as I can tell, is required for install MonetDB4-server): it doesn't compile with the version of JDBC shipped in Sun JDK 6. Basically, the JDBC interfaces have been extended and so we get errors about 'class is not abstract and does not override method ...'. I fixed this the first time by adding stubs that just threw OperationNotSupportedException. Then it compiled.
I made a try with this in the 1_6 branch, but never finished, because amongst others, it makes JDBC incompatible with 1.4 and 1.5 Java compilers. This is a bug, and the solution is to have configure check for Java 1.4 or 1.5, and abort otherwise.
This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users