From: | Federico Di Gregorio <fog(at)initd(dot)org> |
---|---|
To: | psycopg(at)postgresql(dot)org |
Subject: | Re: Range Type Support |
Date: | 2012-09-18 17:17:39 |
Message-ID: | 5058ACB3.5000501@initd.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | psycopg |
On 18/09/2012 19:07, Daniele Varrazzo wrote:
> On Tue, Sep 18, 2012 at 5:57 PM, Jonathan S. Katz
> <jonathan(dot)katz(at)excoventures(dot)com> wrote:
>>> Hi,
>>>
>>> I am using range types in an application I am writing and am
>>> planning on writing some mapping to have support with built-in
>>> Python ranges, and some simple extensions for dealing with date
>>> ranges. I am going to write this on my own regardless, but is
>>> anyone working on this for psycopg2? If not, I would be willing
>>> to contribute the code I am working on.
> What is a "built-in Python range"? You mean some Python object to be
> written with the same semantics of a postgres range? (subtype,
> handling of boundaries, empty singleton).
>
>
We'll probably need a range Python type too here.
federico
--
Federico Di Gregorio federico(dot)digregorio(at)dndg(dot)it
Studio Associato Di Nunzio e Di Gregorio http://dndg.it
99.99999999999999999999% still isn't 100% but sometimes suffice. -- Me
From | Date | Subject | |
---|---|---|---|
Next Message | Jonathan S. Katz | 2012-09-18 17:20:59 | Re: Range Type Support |
Previous Message | Federico Di Gregorio | 2012-09-18 17:16:45 | Re: Range Type Support |