Re: Efficient date range search?
От | Jean-Luc Lachance |
---|---|
Тема | Re: Efficient date range search? |
Дата | |
Msg-id | 3DA1D999.D355DB0C@nsd.ca обсуждение исходный текст |
Ответ на | Re: Efficient date range search? ("Shridhar Daithankar" <shridhar_daithankar@persistent.co.in>) |
Список | pgsql-general |
DEFAULT 'infinity' is much better than my DEFAULT '9999-12-31', I agree. Bruno Wolff III wrote: > > On Mon, Oct 07, 2002 at 13:32:09 -0400, > Jean-Luc Lachance <jllachan@nsd.ca> wrote: > > Alvaro Herrera wrote: > > > > > > On Mon, Oct 07, 2002 at 12:11:35PM -0400, Jean-Luc Lachance wrote: > > > > Shridhar Daithankar wrote: > > > > > Create an index on died field. And query like > > > > > > > > > > select * from pets where died < "last year july 4 7:01 PM; > > > > > > > If the pet is still alive today died would be NULL and the where clause > > > > would not be true. > > > > > > In that case check for NULL explicitly, > > > > > > select * from pets where died > [date] or died is null; > > > > > > Then you're back to whole table scan... :( > > You could use 'infinity'::timestamp as a code for pets that are currently > alive instead of null.
В списке pgsql-general по дате отправления: