[DB-SIG] mxODBC is truncating BLOBs when reading them

[Friedlander Paul]

Thanks for the info. Ultimatly, I want to be DB agnostic and be able to =
use
SQL server also.

-----Original Message-----
From: Gerhard H=E4ring [mailto:gerhard.haering@gmx.de]
Sent: Thursday, July 18, 2002 5:12 PM
To: 'db-sig@python.org'
Subject: Re: [DB-SIG] mxODBC is truncating BLOBs when reading them


* Friedlander Paul <PaulFriedlander@Danfoss.com> [2002-07-18 21:50 =
+0200]:
> Thanks for getting back to me.
>=20
> First of all, here is the traceback:
>=20
> >>> c.execute("SELECT raw_data FROM datasets LIMIT 1")
> >>> a =3D c.fetchall()
> Traceback (most recent call last):
>   File "<interactive input>", line 1, in ?
> Warning: ('01004', -2, 'Fetched item was truncated.', 3480)
>=20
> As for the setup. I am using ActivePython V2.2 and the latest stable
> release of mxODBC. Postgres is running on a Linux box and I am =
running
> the client on Windows 2000.

Just FYI: you can also use pyPgSQL (even psycopg has a win32 port now)
on win32, which won't go thru the additional ODBC layer.

Gerhard
--=20
mail:   gerhard <at> bigfoot <dot> de       registered Linux user =
#64239
web:    http://www.cs.fhm.edu/~ifw00065/    OpenPGP public key id =
AD24C930
public key fingerprint: 3FCC 8700 3012 0A9E B0C9  3667 814B 9CAA AD24 =
C930
reduce(lambda x,y:x+y,map(lambda
x:chr(ord(x)^42),tuple('zS^BED\nX_FOY\x0b')))