From: | Herouth Maoz <herouth(at)oumail(dot)openu(dot)ac(dot)il> |
---|---|
To: | pgsql-sql(at)postgreSQL(dot)org |
Subject: | RE: [SQL] indexing a datetime by date |
Date: | 1999-03-30 11:59:14 |
Message-ID: | l0311070ab3266cb423c7@[147.233.148.140] |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-sql |
At 06:07 +0200 on 30/03/1999, Jackson, DeJuan wrote:
>
> Part of the problem is that PostgreSQL Assumes that a functions value will
> change each time it is required, therefore automatic table scan and the
> function is called for each row.
> Try using 'now'::date instead of now()::date
How about using the ANSI standard CURRENT_DATE instead of either? It's
already of type date. Or is it considered a function call?
Herouth
--
Herouth Maoz, Internet developer.
Open University of Israel - Telem project
http://telem.openu.ac.il/~herutma
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 1999-03-30 13:58:32 | Re: [HACKERS] Re: Are large objects well supported? Are they considered very stableto use? |
Previous Message | Dmitry Samersoff | 1999-03-30 10:58:51 | Re: [HACKERS] libpq++ |
From | Date | Subject | |
---|---|---|---|
Next Message | Ralf Weidemann | 1999-03-30 13:38:06 | sorting by date & time in descending order ?? |
Previous Message | Herouth Maoz | 1999-03-30 11:51:16 | Re: [GENERAL] Returning an integer from a date |