| From: | Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com> |
|---|---|
| To: | Federico Di Gregorio <fog(at)dndg(dot)it> |
| Cc: | psycopg(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Integration of Psycopg with XTA |
| Date: | 2018-10-03 12:52:43 |
| Message-ID: | CA+mi_8aTsj2d+kyrz+86ZOZ8Srno0T5Px6w+SWqfw5iiSPBkcA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | psycopg |
On Wed, Oct 3, 2018 at 1:44 PM Federico Di Gregorio <fog(at)dndg(dot)it> wrote:
>
> On 10/03/2018 02:37 PM, Daniele Varrazzo wrote:
> > On Wed, Oct 3, 2018 at 1:28 PM Federico Di Gregorio<fog(at)dndg(dot)it> wrote:
> >
> >>> This is interesting because PyCapsule is for sure a "clean" way to pass
> >>> the pointer from Psycopg to XTA.
> > Fog, maybe it's worth adding the capsules for PGconn and PGresult to
> > the objects interface and document them? Can do that for psycopg 2.8.
>
> If it works I'd add it (and document it as an "internal" extension point
> used by other C-level modules) for 2.8, yes.
>
> By PGresult you mean adding it on the cursor, or the connection?
Yes, i'd say a _pgconn attribute or _get_pgconn() method on the
connection, a _pgresult thing on the cursor.
By the way a read-only attribute as per your implementation seems
appropriate to me. Christian, why do you think a function would be
better?
-- Daniele
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Federico Di Gregorio | 2018-10-03 13:03:52 | Re: Integration of Psycopg with XTA |
| Previous Message | Federico Di Gregorio | 2018-10-03 12:44:39 | Re: Integration of Psycopg with XTA |