public inbox for [email protected]
help / color / mirror / Atom feedbug in handling Postgres bytea type?
2+ messages / 2 participants
[nested] [flat]
* bug in handling Postgres bytea type?
@ 2022-12-23 02:53 Christopher Bader <[email protected]>
0 siblings, 1 reply; 2+ messages in thread
From: Christopher Bader @ 2022-12-23 02:53 UTC (permalink / raw)
To: [email protected]
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
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: bug in handling Postgres bytea type?
@ 2022-12-23 02:58 Daniele Varrazzo <[email protected]>
parent: Christopher Bader <[email protected]>
0 siblings, 0 replies; 2+ messages in thread
From: Daniele Varrazzo @ 2022-12-23 02:58 UTC (permalink / raw)
To: Christopher Bader <[email protected]>; +Cc: [email protected]
On Fri, 23 Dec 2022 at 02:54, Christopher Bader <[email protected]> wrote:
> 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.
>
Define not correct.
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2022-12-23 02:58 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-12-23 02:53 bug in handling Postgres bytea type? Christopher Bader <[email protected]>
2022-12-23 02:58 ` Daniele Varrazzo <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox