Data source name not found, and no default driver specified about pypyodbc

[GoogleCodeExporter]

Same problem with:

pypyodbc trunk
python-2.7.3 / pypy-1.9
unixODBC-2.3.1
Gentoo Linux

Original comment by [email protected] on 8 Oct 2012 at 1:58

[GoogleCodeExporter]

Original comment by [email protected] on 8 Oct 2012 at 1:33

• Changed state: Accepted
• Added labels: OpSys-Linux

[GoogleCodeExporter]

This should now work fine with the svn head / hg tip revision.

Relevant changeset: 
https://bitbucket.org/jiangwen365/pypyodbc/commits/23cbcaaea1db6bab505ca7b9b404b
893cfb7dd6f

Previously, when using wide Python build with connection string 
'DRIVER={driver};...', only the first character (uppercase D) is passed to 
unixODBC, thus causing the error "Data source name not found, and no default 
driver specified"

Original comment by [email protected] on 14 Jan 2013 at 7:48

[GoogleCodeExporter]

Thanks for the feed back, I'm going to close the ticket.

Original comment by [email protected] on 14 Jan 2013 at 7:52

• Changed state: Started

[GoogleCodeExporter]

Hi Felix, can you try the latest 0.9.3 and see if this problem has been fixed?

Original comment by [email protected] on 15 Feb 2013 at 2:47

[GoogleCodeExporter]

Original comment by [email protected] on 22 Feb 2013 at 5:44

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by [email protected] on 23 Mar 2013 at 11:41

[GoogleCodeExporter]

I know this bug was closed a while ago, but I am having the exact same problem 
on Mac OS X with pypyodbc v.1.3.3, python 2.7.5. Is there any chance this was 
only fixed for Linux, and not Mac?

Original comment by [email protected] on 1 Jul 2014 at 9:00