Re: [psycopg] Turbo ODBC - Mailing list psycopg

From Daniele Varrazzo
Subject Re: [psycopg] Turbo ODBC
Date
Msg-id CA+mi_8Z5texpMHckgmrQbHSQ2jzUcPfcFBnrqDoOYHHi1QzDzg@mail.gmail.com
Whole thread Raw
In response to Re: [psycopg] Turbo ODBC  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: [psycopg] Turbo ODBC  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List psycopg
ISTM there has to be a fundamental switch in how psycopg uses the
libpq: it should use, at least for what these large objects are
concerned, a binary data type and asking for a binary result
(https://www.postgresql.org/docs/9.6/static/libpq-exec.html#LIBPQ-PQEXECPARAMS),
right?

-- Daniele

On Tue, Jan 17, 2017 at 4:31 PM, Jim Nasby <Jim.Nasby@bluetreble.com> wrote:
> On 1/17/17 9:16 AM, Koenig, Michael wrote:
>>
>> For the NumPy functionality, NULL values are handled by returning masked
>> arrays (https://docs.scipy.org/doc/numpy/reference/maskedarray.html) instead
>> of plain arrays.
>
>
> Oh, interesting. That's the same representation Postgres uses internally as
> well. I hope to explore this further in plpython at some point.
>
> --
> Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
> Experts in Analytics, Data Architecture and PostgreSQL
> Data in Trouble? Get it in Treble! http://BlueTreble.com
> 855-TREBLE2 (855-873-2532)
>
>
> --
> Sent via psycopg mailing list (psycopg@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/psycopg


psycopg by date:

Previous
From: Jim Nasby
Date:
Subject: Re: [psycopg] Turbo ODBC
Next
From: Jim Nasby
Date:
Subject: Re: [psycopg] Turbo ODBC