On Mon, 2004-04-26 at 09:41, Dossy wrote: > It is? What does the nsunixodbc module do that nsodbc currently > doesn't, *other* than the newly implemented support for turning off > autocommit and explicit ending of transactions with COMMIT or ROLLBACK.
I think both nssolid and nsodbc use the older odbc2 API, the "unixodbc" module now has support for compiling either odbc2 or odbc3 API's, also, Bob Woodside, who added the 2/3 options noted the following: ------------- 1) It supports more ns_ functions (DbFn_DbType, DbFn_Select, DbFn_DML) than nsodbc, and lacks none that nsodbc has. 2) It has more informative logging. 3) I've tested it with both unixODBC and iODBC (libiodbc), and feel comfortable that it works well. (I haven't tried the DbFn_DML function yet, though.) 4) I've already made an ODBC3 version based on it (actually, it will conditionally build to use either the ODBC2 or ODBC3 API). -------- I've tested all the ns_db and ns_odbc APIs and they work. Also, Bob and you (and now I) agree there should be one version in the end for both platforms. However, the ODBC support is still very thin even in the "unixodbc" module. I am going to commit myself to getting this to work under windows when the time comes. I have VC6, and I'd like to see AOLserver running on Win, especially since I'm starting to take a liking to MimerSQL, which has a high level of SQL-99 and SQL-2003 conformance, is easy to install and maintain, is reasonably priced, and free for development use. I just finished adding the transaction support to Bob's changes. I'm open to any API changes for ns_odbc, which at present is stuck in the format of "ns_odbc option dbHandle". tom jackson -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
