No takers, huh? I have taken the time to study the JDBC driver and... I don't know Java at all... and the driver is so specific to the java class structure that it is very difficult to follow :)
I'm thinking in the short term the best thing to do is take a shortcut. My target environment is web sites with a lot of concurrency, where ODBC.NET is not proving to be very reliable using the SAPDB ODBC driver. My idea is to not do a full driver, just a highly optimized class that does primarily one thing: returns DATASET objects from SELECT statements / stored procedures from a SAPDB database. Just something to get around the performance bottleneck for the most common operation in most web sites (database reads). Fall back to using the ODBC.NET driver for all other tasks (writes, cursors, etc). Based on what I've studied with other drivers, there can be a 4x or higher performance gain going with a native dotNet driver and not using the ODBC.NET driver. This is the approach that some driver developers are taking with PostgreSQL and MySQL, or at least the natural starting point. Any java programmers out there willing to help me get started? My first goal is to figure out the existing code. First steps are how to assemble a network packet to send to a SAPDB server. That means unraveling the username/password SQL command encoding, assembling the packet, parsing back the results. SAP team... my questions about the future JDBC driver releases is still unanswered. Please. Stephen -----Original Message----- From: Stephen Gutknecht (SAPDB) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 25, 2002 11:10 AM To: [EMAIL PROTECTED] Subject: Porting the JDBC driver to dotNet I've just come to realization that there is a modern code base with native SAPDB socket driver... the JDBC driver! The Java driver is described as a "Type 4 driver (Connects to the database using the proprietary SAP DB socket protocol)" -- which means, in theory, it could provide a good reference example of the SADPB socket protocol. Anyone working on a port of this :) Anyone want to help on a port of this? SAPDB team... previous queries have gotten responses that a new Win32 driver is not on coming anytime soon (no OLEDB, no native dotNet). Porting the JDBC driver makes sense to you? Also - is the download on sapdb.org the _latest_ JDBC driver? I don't want to spend time working with it to find out that it is obsolete. Is a JDBC 3.0 update in the works I may not have time to do this, just considering the options. Thank you. Stephen _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
