Vernon Cole wrote:
I ran into the same problem using adodbapi. I tracked it down to the COM
call which errored out, and decided that maybe it was a Microsoft problem
and ignored it, just leaving the application broken on that feature. If
pyODBC can do it, then the problem must be in the COM
On 28/05/2010 3:26 AM, Vernon Cole wrote:
I can throw together a quick example of the failure if that will help
with debugging. It involves a sample SQL data table that must be
imported for the test and is not small (several recorded telephone calls
as blobs)-- so I will only do it if needed.
Hi,
When a ms sql server database column was changed to varchar(max), my
python code became unable to read that column. no matter the actual
value, python sees it as '\x00'. I use sql server 2008, python 2.4, and
pywin32-214. it had worked when the column was a fixed size varchar, eg
varchar(max) columns are like CLOBs, character large objects, and I'm not
sure how well that odbc module handles them. I ended up switching to
pyODBC which does handle them. Unfortunately it might not be just a drop-in
replacement, and pyODBC does have its own issues. But so far it's working
I ran into the same problem using adodbapi. I tracked it down to the COM
call which errored out, and decided that maybe it was a Microsoft problem
and ignored it, just leaving the application broken on that feature. If
pyODBC can do it, then the problem must be in the COM routines in pywin32.
I
