From: | Szymon Guz <mabewlun(at)gmail(dot)com> |
---|---|
To: | Jan Urbański <wulczer(at)wulczer(dot)org> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: storing plpython global pointer |
Date: | 2013-05-28 12:22:13 |
Message-ID: | CAFjNrYuzRSi2c_4=+qvV2qDNLkmY6_Qs_Ghq4QqSFa7rzfARjg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 28 May 2013 14:15, Jan Urbański <wulczer(at)wulczer(dot)org> wrote:
> On 28/05/13 14:04, Szymon Guz wrote:
>
>> Hi,
>> I need to store a global pointer for plpython usage. This is a PyObject*
>> which can be initialized per session I think
>>
>> Where should I keep such a pointer?
>>
>
> Hi,
>
> you probably could use a global variable, similar to PLy_interp_globals
> that's defined in plpy_main.c.
>
> Another method would be to expose the Decimal constructor in the plpy
> module. You could modify plpy_plpymodule.c to import decimal and expose the
> Decimal constructor as plpy.Decimal.
>
> Best,
> Jan
>
I think I'd rather go with the first solution, as this function should not
be accessible inside the plpython function. That's what I was thinking
about as well, but I wasn't sure.
thanks,
Szymon
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2013-05-28 12:36:39 | Re: Extent Locks |
Previous Message | Andrew Dunstan | 2013-05-28 12:21:50 | Re: Unsigned integer types |