From pkraus at pelsupply.com Fri Jun 24 08:34:15 2011 From: pkraus at pelsupply.com (Paul Kraus) Date: Fri Jun 24 13:34:41 2011 Subject: [egenix-users] Ubuntu 64bit unixODBC (from source 2.3.0), mxodbc Message-ID: Let me start by saying that iSQL works without issue. My app is running on a 64 bit version of ubuntu using unixODBC 2.3.0 connecting to a proprietary db (Thoroughbred) using their 64bit driver which I am 99.9% sure is based on sybase. Using your two most recent versions 3.1.X when sending a select query I get back random garbage on any null fields. I would assume this would happen in any transaction but selects are where i have seen it happen and its 100% reproducible. Using your older 3.0.4 version everything appears to work fine and null strings come back just fine however my app will just randomly die and a segfault for mxodbc is recorded in /var/log/messages. I have a production ready app that my customer was expected to go live with today but I had to push it do to the random crashes. This issue is costing me money by the day. To be clear I don't think this is an mx.odbc issue i think it has something to do with the fact that i am running on 64 bit but was hoping that someone on this list had the same issue and has a work around that doesn't involved having to deploy on a 32bit machine. TIA, PK -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20110624/f4a11955/attachment.htm