From: | Nelson Green <nelsongreen84(at)gmail(dot)com> |
---|---|
To: | pgsql <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Programmatic access to interval units |
Date: | 2014-12-03 01:15:04 |
Message-ID: | CAGo-KZk+cC+FKJS1qezRpMDmM+J2J9m8DsH=2hN0RanNx482vQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Dec 2, 2014 at 3:48 PM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> On Tue, Dec 2, 2014 at 12:40 PM, Nelson Green <nelsongreen84(at)gmail(dot)com>
> wrote:
> > In the line: IF LOWER(_unit) NOT IN (SELECT interval_unit ..., I would
> > rather
> > query a catalog table for the interval unit names if possible. That would
> > then
> > compensate for any changes to those values in the future.
> >
> > When I meant do this in C, I was referring to rewriting this function in
> C
> > instead of Pl/pgSQL.
> >
> > I hope this helps you understand what I am asking, and apologies for not
> > being
> > more specific up front.
>
> I was the one that was confused -- heh. I mis-understood the original
> email and thought you were trying to validate interval output vs
> interval input.
>
> merlin
>
But you took time to work with me, and I appreciate that.
Thanks,
Nelson
From | Date | Subject | |
---|---|---|---|
Next Message | mongoose | 2014-12-03 05:05:53 | Re: Merge rows based on Levenshtein distance |
Previous Message | Joshua Boyd | 2014-12-02 23:50:29 | Re: Postgres 9.2 PITR testing to before DROP DATABASE ends up removing file system files |