From: | Francisco Olarte <folarte(at)peoplecall(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | Chuck Martin <clmartin(at)theombudsman(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Query not producing expected result |
Date: | 2019-05-01 17:58:53 |
Message-ID: | CA+bJJbyUxwWux3NQKiebsdbzpb_52M16Ho1oxm5zM6cdUm-tSw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Adrian..
On Wed, May 1, 2019 at 7:50 PM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> wrote:
> I should have made it clearer, my suggestion was mostly directed at
> Franciso's example.
...
> For this sort of thing, I have found range types to be a time and sanity
> saver. Just throwing it out there.
I've had problems with the functions, being used to the [start,end)
notation on paper. I'll look at them again.
But anyway, after so many years of not having intervals and operators,
I read "$start<= $val and $val < $end" as "$val in [$start,$end)", I
think it shares brain paths with "for(;;)" parsing to "forever /
loop". I would like to have the "$start <= $val < $end" which some
language whose name I do not remember has, for complex $vals.
Francisco Olarte.
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2019-05-01 18:04:44 | Re: Query not producing expected result |
Previous Message | Chuck Martin | 2019-05-01 17:58:35 | Re: Query not producing expected result |