I'm not as worried about being database portable since where I work is Sybase IQ (data warehouse) centric and probably will be for quite sometime to come.
Plus, what I'm doing with the Sybase JDBC driver IS portable to any Java application be it an app server or standalone as long as what comes back from the JDBC call is Sybase's implementation of the ResultSet class. I think that is a reasonable expectation. Believe me, I'd rather not have to use the Sybase result set functions to write large amounts of data to CLOB/BLOB fields, but that's the only way it works in Sybase land. Sybase only supports 4-6k CLOB/BLOB write via the standard ResultSet interface's rs.setBytes() call. Like I said, I'm only "a bit concerned" about having to import JBoss specific classes to make the JDBC code work as it did before. I can also do class instance checking as well to toggle the use of JBoss specific class on and off. However, I still have to import the JBoss specific class to do the check. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3837978#3837978 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3837978 ------------------------------------------------------- This SF.Net email is sponsored by: GNOME Foundation Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event. GNOME Users and Developers European Conference, 28-30th June in Norway http://2004/guadec.org _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
