| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dmitry Tkach <dmitry(at)openratings(dot)com> |
| 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:52:41 |
| Message-ID: | 15184.1059411161@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc pgsql-sql |
Dmitry Tkach <dmitry(at)openratings(dot)com> writes:
> Why not get rid of 'now' alltogether? Are there any cases when it is
> actually useful as opposed to now()?
Data entry. You don't necessarily have the option to invoke a function,
as opposed to just sending a string for the datetime input parser.
(It would be rather difficult for an application to allow this one case
without permitting SQL-injection attacks, I'd think.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dmitry Tkach | 2003-07-28 17:06:27 | Re: Very strange 'now' behaviour in nested triggers. |
| Previous Message | Dmitry Tkach | 2003-07-28 16:43:43 | Re: Very strange 'now' behaviour in nested triggers. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dmitry Tkach | 2003-07-28 17:06:27 | Re: Very strange 'now' behaviour in nested triggers. |
| Previous Message | Josh Berkus | 2003-07-28 16:47:21 | Re: Problem using Subselect results |