| From: | Dmitry Tkach <dmitry(at)openratings(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Denis Zaitsev <zzz(at)anda(dot)ru>, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Very strange 'now' behaviour in nested triggers. |
| Date: | 2003-07-28 16:43:43 |
| Message-ID: | 3F2552BF.5060100@openratings.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc pgsql-sql |
Tom Lane wrote:
>
>I put up a proposal in pgsql-hackers to change this behavior:
>http://archives.postgresql.org/pgsql-hackers/2003-07/msg00818.php
>If we made that change then the "wrong" way of defining the default
>would fail in an obvious fashion --- the 'now' would get reduced to a
>particular time immediately at CREATE TABLE. Doubtless this would annoy
>some people, but the "right" way of defining the default isn't really
>any harder, and it would save folks from getting burnt in corner cases,
>like you were.
>
>Any comments?
>
>
>
Why not get rid of 'now' alltogether? Are there any cases when it is
actually useful as opposed to now()?
Dima
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-07-28 16:52:41 | Re: Very strange 'now' behaviour in nested triggers. |
| Previous Message | Fernando Nasser | 2003-07-28 15:49:41 | Re: Another exception (Transaction level) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2003-07-28 16:47:21 | Re: Problem using Subselect results |
| Previous Message | Bruno Wolff III | 2003-07-28 16:41:29 | Re: Problem using Subselect results |