Hi, maybe I didn't phrase my question correctly. I'm using a SGI machine
running Irix and going to be using a mySQL db on a Linux box behind a
firewall. Since I will set up a tunnel with ssh2 to forward port 3306, it
will appear to the Irix system that the db exists locally. Now here is what
I'm confused about: Do I 1) install both iODBC and myODBC on the Irix
system? or 2) install iODBC on the Irix one and myODBC on that Linux machine
where the mySQL db physically located? Thanks!
Wen
-----Original Message-----
From: Venu [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 24, 2001 9:33 AM
To: Werner Stürenburg; Wen Tien
Cc: [EMAIL PROTECTED]
Subject: RE: myODBC?
Hi !!!
)-----Original Message-----
)From: Werner Stürenburg [mailto:[EMAIL PROTECTED]]
)Sent: Friday, August 24, 2001 5:59 AM
)To: Wen Tien
)Cc: [EMAIL PROTECTED]
)Subject: Re: myODBC?
)
)
)In my understanding, myODBC is a middleware for programs which
)don't know how to deal directly with mySQL. So if you use perl or
)php, you won't ever use ODBC, as this only slows things down,
)obviously. ODBC is kind of a workaround in my understanding.
)
)Please correct me, if I'm wrong.
)
)Wen Tien schrieb am Freitag, 24. August 2001, 14:39:55:
)
)> Hi,
)> I am a newbie that has a question about what exactly is
)myODBC (for Unix)
)> doing. Is myODBC, 1) a "wrapper" over the mySQL database to
)make it conform
)> to the ODBC interface or 2) a plug-in driver that goes with a manager
)> program to allow the access of mySQL db? I am using an Irix machine that
)> tries to use a mySQL db on a Linux box (natively via port
)forwarding) so I'm
)> trying to decide where to install what... thanks.
)
MyODBC is a ODBC Driver for MySQL. The current version is fully conformed to
MS ODBC 2.x Specifications. So you can use the driver to access MySQL as per
this specifications.
Coming to the second one, yes, MyODBC works fine with all major driver
managers such as MS ODBC DM, iODBC, unixODBC and Merant ODBC DM. Also it
works in a stand alone mode too when you link the static library of the
driver to your application. In this case no DSN issue will be coming. You
can use DSN less connection, by specifying proper connection fields. The
only drawback in this case (for any odbc driver ) is it can only talk to
MySQL server, and it can't talk to any other, but its not the case when
going through the manager.
Regards
Venu
--
For technical support contracts, go to https://order.mysql.com/
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Venu <[EMAIL PROTECTED]>
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Developer
/_/ /_/\_, /___/\___\_\___/ Woodside, California USA
<___/ www.mysql.com
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
