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 pretty well for us.
http://code.google.com/p/pyodbc/ On Thu, May 27, 2010 at 10:56 AM, John <j...@saponara.net> wrote: > 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(1000). > essentially my code is: > > connectionString=r"driver={SQL Server Native Client > 10.0};server=...;uid=...;pwd=...;database=..." > connection=odbc.odbc(connectionString) > cursor=connection.cursor > cursor.execute("select ...") > cursor.fetchall() > > Could anyone suggest what the problem might be? > > Thanks, > John > > >
_______________________________________________ python-win32 mailing list python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32
