[Mono-osx] ODBC - MySql - Data source name not found

David Rivera mithril at me.com
Sun Dec 20 17:58:32 EST 2009


Ouch, hmmm...

Does anyone know where the odbc.ini and odbcinst.ini files should be located
for the libraries that mono uses for odbc to find them?  I've tried placing
them in /Library/ODBC, /Users/username/Library/ODBC and /etc, all locations
in my searching on the net that iODBC might search for them, but no go it
seems.  I can get iodbctest to connect properly, which I assume is part of
the iODBC system, which it looks like is what mono should be using to
connect via odbc, but any mono app I use still fails.

-David Rivera


FairgroundTown wrote:
> 
> I never solved it :(
> 
> I found the source code to the mono class, but it is litterally a one-line
> wrapper for the native code, and the "bug" is in there... or possibly in
> the parts if the framework which actually execute the native call.
> Whatever, I wasn't going to be able to fix it, so I'm ashamed to say that
> I gave up, and paid-out for a copy of parallels so I could do it in
> Windows.
> 
> 
> 
> David Rivera wrote:
>> 
>> I am having this issue as well, anyone out there have any info on getting
>> ODBC connection to work on OSX?
>> 
>> -Dave Rivera
>> 
>> 
>> FairgroundTown wrote:
>>> 
>>> (I realize this is kind-of an edge case.)
>>> 
>>> I am on OSX 10.4, running Mono 2.4.2.3.
>>> 
>>> I have both user and system ODBC DSNs set up - to MySql - and the
>>> connector works in the ODBC Administrator dialog.
>>> 
>>> But from a Mono app, I get 'Data source name not found...' with either
>>> the user or the system connection.
>>> 
>>> I am using the OdbcConnectionStringBuilder and it is producing a
>>> connection string of DSN=mydsn.
>>> 
>>> If I try to use a DSN-less connection, I get exactly the same error,
>>> which is odd, as it suggests that something is failing to parse the
>>> connection string at all???
>>> 
>>> (I have no particular need to use MySql if another database will work -
>>> any recommendations? I do, however, HAVE to use ODBC!)
>>> 
>>> Some hints on another forum that this may have something to do with
>>> unicode naming, but I can't see how to address this on OSX? (The other
>>> post was on Linux.)
>>> 
>>> Thanks
>>> 
>> 
>> 
> 
> 

-- 
View this message in context: http://old.nabble.com/ODBC---MySql---Data-source-name-not-found-tp25994262p26868065.html
Sent from the Mono - OSX mailing list archive at Nabble.com.



More information about the Mono-osx mailing list