2012/4/25 Jasen Betts <jasen@xxxxxxxxxx>: > On 2012-04-25, Valentin Militaru <valentin.militaru@xxxxxxxxx> wrote: >> This is a multi-part message in MIME format. >> --------------050404030901030607030308 >> Content-Type: text/plain; charset=UTF-8; format=flowed >> Content-Transfer-Encoding: 7bit >> >> What about using >> >> WHERE f BETWEEN '2012-04-23 00:00:00' AND '2012-04-24 00:00:00'? >> > > that could match the first microsecond of 2012-04-24 > otherwise not a prolem :) > > another option is BETWEEN '2012-04-23 00:00:00' AND '2012-04-23 23:59:60' > > or even BETWEEN '2012-04-23 00:00:00' AND '2012-04-23 23:59:60.999999' > > these are reliant on documented behaviours, but documented > inosyncratic behaviours, behaviours that could potentially be improved. > such that it woulkd no longer be reliable. > >>> you have to do it the long way >>> >>> f>= '2012-04-23 00:00:00' AND f< '2012-04-24 00:00:00' >>> > > this way is mathematically correct and relies on standard guaranteed > behaviours only. > > -- > ⚂⚃ 100% natural Correct Jasen! In my opinion the use of BETWEEN (as it is currently defined) makes very little sense (if any) at least for time stamps. What I've seen so far with time periods are always defined as either "[...)" or "(..]". -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
