While it is true that JBDC works and is fairly easy to setup, it must run through the VM, and will not have the same level of performance as ODBC.
This is not entirely true. On the first call it is slower, but on subsequent calls to the driver the JVM has cached the driver in a compiled state. The JVM is also loaded at startup by the server and not unloaded until the server process shuts down so there is no overhead from starting the JVM. Most of the performance issues are more likely to be in the implementation of the jdbc driver.
First install witango server v. 5.01.065. You should do this first, cuz it can mess with your ODBC frameworks, making your frameworks point to the default apple version of iODBC.
This is not correct. The server does not use frameworks or modify them. The server loads the library directly based on the value of ODBCDMLIBRARY in the witango.ini. The dev studio does use the frameworks as it is a carbon app.
Now here is the key, in order for witango to see these DSNs, there are a couple of environment variables that must be set. The best place to set these variables is in a startup item, and the witango installer should have made a startup item for you with the following code in it:
# Set up environment for ODBC driver manager # ODBCINI=/Library/ODBC/odbc.ini export ODBCINI ODBCINSTINI=/Library/ODBC/odbcinst.ini export ODBCINSTINI
This sets the env. vars so witango will see your system dsns. If for some reason you want to use User DSNs ( you shouldn't), then you would have to modify the above environment variable to point to the correct ini files.
This is very important because if these environment variables are not set in the witango server's environment, when it loads the iodbc driver manager the iodbc driver manager will go off and search for an odbc.ini file in different locations and if it cannot find an odbc.ini file will create hidden .odbc.ini files in hidden directories. The startup script for the witango server process is /Library/StartupItems/Witango5/Witango5. You can modify this file to use any odbc.ini file on your system. Also make sure that the odbc.ini file can be read by the witango user as it owns the witango process.
You can also download the latest iodbc source code and compile and install it if you have installed the apple developer tools. It has come a long way since puma/jaguar days and is no longer a black art. It has an OS X read me and only takes 3 commands in a terminal window to compile and install it.
Everyone using OS X should also partition Apple and get them to upgrade the old iodbc that ships in Panther and fix the ODBC Administrator app. The more people that ask them the more likely it is that it will happen. Keep sending them request to update it.
Witango Support
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
