TOTALLY agree on oracle, JDBC is about 100x easier to implement, than
OCI, and even ODBC.
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/
On Jul 15, 2006, at 8:48 AM, Dale Graham wrote:
Yes, I have to admit my only experience has been with MySQL and
Oracle -- JDBC has been terrific with both of them (and Oracle ODBC
was a *horror* - luckily before JDBC, we could at least use Oracle
OCI, which was much better but still had some trials for setup).
You *do* need to keep your JDBC drivers concurrent with your DB
version, however.
On Jul 15, 2006, at 11:42 AM, Robert Garcia wrote:
It really depends on the database, I have seen some JDBC driver/
systems that are much less reliable than the ODBC counterpart, and
vice versa. You have to go with what works best with your DB.
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/
On Jul 15, 2006, at 8:36 AM, Roland Dumas wrote:
I once switched to JDBC and it was unreliable. lotsa crashes on
the server. Server is happy with ODBC. It's my dev workstation
that's weird. The weirding event was updating to 10.4.6. It
killed odbc.
On Jul 15, 2006, at 3:53 AM, Dale Graham wrote:
Have you considered a switch to JDBC? In our experience it's
far far less trouble to use than ODBC. Esp on the Mac.
On Jul 15, 2006, at 1:30 AM, Robert Garcia wrote:
The actual drivers crash witango, work great everywhere else.
You have to use myodbc 3.5.1, it is a pain, I have done this a
bunch of times, you may want to contact me off list.
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/
On Jul 14, 2006, at 5:47 PM, Roland Dumas wrote:
getting deeper into difficulty....
could not get myodbc drivers to work at all. hunted here and
there to look for odbc.ini files and can't make heads or tails
of what is right and what is in the wrong place. I found a
driver from ActualTechnologies that enabled me to get data
into excel through the query application, but those drivers
crash witango studio. The openlink mysql driver, which is
licensed to connect to only one database, disappeared from
witango studio. it seems no longer to see any user DSNs and I
can't use the openlink as a system DSN. So, myodbc doesn't
work, Actual doesn't work, and openlink doesn't work with
witango studio.
is there a way I can simply start over and strip out
everything and start from scratch?
On Jul 11, 2006, at 11:25 PM, Robert Garcia wrote:
I found it, I have no idea why, but in the older UDA 5.2
version of the manager, the user DSNs were stored in ~/
library/odbc/odbc.ini , however, with the latest manager, UDA
6.0 from openlink, user dsns are being stored in ~/.odbc.ini
which is hidden, cuz of the dot at begin. I have no idea why
they did this, but the new UDA 6 openlink manager is the
latest from iODBC, and is universal binary. The trick to
using it, is to download one of their demos, and doing a
custom install, and NOT installing the driver, just the
manager. As far as I know, the framework and iodbc libs are
not hindered at all, just the driver, then you can use the
myodbc driver.
So, other than the new location for the user dsns, the
instructions from witango support should be fine, the system
dsns are still stored in /library/odbc/odbc.ini
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/
On Jul 11, 2006, at 12:27 PM, Roland Dumas wrote:
I have their manager. All my DSNs failed after upgrading to
OS 10.4.6 and I couldn't find a way to make them live again.
That's what I'm trying to do. I installed the MyODBC driver
- latest version, but can't get the driver configured in
either ODBC manager. Have no idea what to put in the setup
config.
On Jul 11, 2006, at 10:58 AM, Robert Garcia wrote:
You don't need to buy openlink, you can use the SDK, and
use their manager, and use the myodbc 3.5.1 directly from
mysql. Also, openlink limits you to one connection, with
their driver, but not with other installed drivers. So just
use their manager, but not the driver.
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/
On Jul 11, 2006, at 10:06 AM, Roland Dumas wrote:
When I updated my OS to 10.4.6 on my workstation, my ODBC
died dead. I couldn't figure out how to revive it, so
purchased an openlink driver for $100, which installed and
worked. The openlink only allows one connection to one
database. For more, the price goes through the roof. So,
I'm back trying to figure out how to reinstall the myODBC
driver so that it works.
The official installer works fine, and the instructions
show how to create DSNs, but NOT how to configure the
driver. I haven't a clue how to do this. What to put in
the "driver" and "setup" fields in the ODBC
configuration._______________________________________________
_________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/
maillist.taf
______________________________________________________________
__________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/
maillist.taf
_______________________________________________________________
_________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/
maillist.taf
________________________________________________________________
________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/
maillist.taf
_________________________________________________________________
_______
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/
maillist.taf
__________________________________________________________________
______
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/
maillist.taf
___________________________________________________________________
_____
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
____________________________________________________________________
____
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
_____________________________________________________________________
___
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
______________________________________________________________________
__
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
