[unixODBC-dev] Problems with the way unixODBC switched to 64-bit SQLLEN

[M.-A. Lemburg]

Nick Gorham wrote:
> M.-A. Lemburg wrote:
>> I'd suggest to quickly move to unixODBC 2.3.0 to signal
>> the change in API to the user and bump the .so version
>> number to 2.0.0 (as already implemented by Fedora)
>> to clear up the situation again.
>>
>> Thanks,
>>   
> Yes, there is merit in that, unless others have a issue with that I will
> move 2.2.15 to 2.3.0 when it gets to the release.

Thanks, that would make things a lot easier.

> If it helps, odbc_config in 2,2,14 and later allows checking of the
> sizeof( SQLLEN ).

Not really: We deliver binaries of mxODBC to our users and the loading
of unixODBC happens at Python module load time.

We'd rather not have to spawn an external process in order to detect
the configuration.

> BTW Mark, I have just commited a fix to 2.2.15pre that solves a python
> related issue, but I dont know if it affected mxODBC

Do we have to get that from CVS or the FTP server ?

Thanks Nick,
-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Source  (#1, Feb 26 2010)
>>> Python/Zope Consulting and Support ...        http://www.egenix.com/
>>> mxODBC.Zope.Database.Adapter ...             http://zope.egenix.com/
>>> mxODBC, mxDateTime, mxTextTools ...        http://python.egenix.com/
________________________________________________________________________

::: Try our new mxODBC.Connect Python Database Interface for free ! ::::


   eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
    D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
           Registered at Amtsgericht Duesseldorf: HRB 46611
               http://www.egenix.com/company/contact/