From: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Jim Nasby <jim(at)nasby(dot)net>, Vik Reykja <vikreykja(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Inputting relative datetimes |
Date: | 2011-08-27 15:11:03 |
Message-ID: | CAEZATCVsZyme9pFFousWdHdTQhxv-m0vzsq6y5zHw6BdWZ7WqA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 27 August 2011 14:14, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> On lör, 2011-08-27 at 12:29 +0100, Dean Rasheed wrote:
>> So Robert and Merlin both expressed concerns that the existing
>> datetime string parsing code is so complicated that adding to it would
>> likely just introduce more bugs.
>>
>> My first thought was 'how hard can it be?' - famous last words :-)
>
> Maybe you can find an existing Perl or Python module that has already
> implemented this. Then the solution might be 5 lines of wrapping this
> into a PostgreSQL function.
>
Ah now that's an interesting idea.
Python's dateutil module seems to come highly recommended, although I
don't find this too encouraging:
>>> dateutil.parser.parse('today', fuzzy=True)
datetime.datetime(2011, 8, 27, 0, 0)
>>> dateutil.parser.parse('tomorrow', fuzzy=True)
datetime.datetime(2011, 8, 27, 0, 0)
>>> dateutil.parser.parse('foobar', fuzzy=True)
datetime.datetime(2011, 8, 27, 0, 0)
Still, there might be something better out there...
Cheers,
Dean
From | Date | Subject | |
---|---|---|---|
Next Message | Dean Rasheed | 2011-08-27 15:36:13 | Re: Inputting relative datetimes |
Previous Message | Magnus Hagander | 2011-08-27 14:35:35 | Re: Cryptic error message in low-memory conditions |