Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #51636
| From | Antoine Pitrou <solipsis@pitrou.net> |
|---|---|
| Subject | Re: Problem with psycopg2, bytea, and memoryview |
| Date | 2013-07-31 09:50 +0000 |
| References | <ktam8i$hj3$1@ger.gmane.org> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.5.1375264264.1251.python-list@python.org> (permalink) |
Frank Millman <frank <at> chagford.com> writes: > > I have some binary data (a gzipped xml object) that I want to store in a > database. For PostgreSQL I use a column with datatype 'bytea', which is > their recommended way of storing binary strings. > > I use psycopg2 to access the database. It returns binary data in the form of > a python 'memoryview'. > [...] > > Using MS SQL Server and pyodbc, it returns a byte string, not a memoryview, > and it does compare equal with the original. > > I can hack my program to use tobytes(), but it would add complication, and > it would be database-specific. I would prefer a cleaner solution. Just cast the result to bytes (`bytes(row[1])`). It will work both with bytes and memoryview objcts. Regards Antoine.
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: Problem with psycopg2, bytea, and memoryview Antoine Pitrou <solipsis@pitrou.net> - 2013-07-31 09:50 +0000
csiph-web