MIME-Version: 1.0
From: Christopher Bader <cbader@zscaler.com>
Date: Thu, 22 Dec 2022 21:53:43 -0500
Message-ID: 
 <CAKvpR7Od=NU2yi=sOf5wiaKU1A+v_T2GJ8+JDdzE1yABFPwyYA@mail.gmail.com>
Subject: bug in handling Postgres bytea type?
To: psycopg@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000de83bd05f075e654"
Archived-At: 
 <https://www.postgresql.org/message-id/CAKvpR7Od%3DNU2yi%3DsOf5wiaKU1A%2Bv_T2GJ8%2BJDdzE1yABFPwyYA%40mail.gmail.com>
Precedence: bulk

--000000000000de83bd05f075e654
Content-Type: text/plain; charset="UTF-8"

I'm having problems reading bytea fields with psycopg2.

Reading a bytea field with cursor.fetchall yields a memoryview object, not
a bytes or bytearray object, and even when the object is explicitly
converted to bytes or bytearray, the result is not correct.

Christopher Bader
Staff Data Scientist
Zscaler

--000000000000de83bd05f075e654
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I&#39;m having problems reading bytea fields with psycopg2=
.<div><br></div><div>Reading a bytea field with cursor.fetchall yields a me=
moryview object, not a bytes or bytearray object, and even when the object =
is explicitly converted to bytes or bytearray, the result is not correct.</=
div><div><br></div><div>Christopher Bader</div><div>Staff Data Scientist</d=
iv><div>Zscaler</div></div>

--000000000000de83bd05f075e654--