Is this intentional or configurable? Other JDBC drivers throw an SQLException in this case which IMHO makes sense because this usually is a programmer error. I've had several occasions when this made debugging a lot harder. if there are reasons why this should be useful it would be great to have this configurable.
would anyone from the sapdb team like to comment? thanks in advance and keep up the good work, robert _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
