| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | josh(at)agliodbs(dot)com |
| Cc: | Martijn van Oosterhout <kleptog(at)svana(dot)org>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Manfred Koizar <mkoi-pg(at)aon(dot)at>, Roland Roberts <roland(at)astrofoto(dot)org>, pgsql-sql(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: [SQL] CURRENT_TIMESTAMP |
| Date: | 2002-09-30 03:53:59 |
| Message-ID: | 14617.1033358039@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers pgsql-sql |
Josh Berkus <josh(at)agliodbs(dot)com> writes:
> Are we still planning on putting the three different versions of now() on the
> TODO? I.e.,
> now('transaction'),
> now('statement'), and
> now('immediate')
> With now() = now('transaction')?
I have no objection to doing that. What seems to be contentious is
whether we should change the current behavior of CURRENT_TIMESTAMP.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-09-30 04:36:34 | Re: [SQL] CURRENT_TIMESTAMP |
| Previous Message | Martijn van Oosterhout | 2002-09-30 03:23:41 | Re: Server to server communication |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-09-30 04:12:24 | Re: CVS split problems |
| Previous Message | Tom Lane | 2002-09-30 03:48:18 | Re: DROP COLUMN misbehaviour with multiple inheritance |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-09-30 04:36:34 | Re: [SQL] CURRENT_TIMESTAMP |
| Previous Message | Mike Sosteric | 2002-09-30 00:12:55 | Re: [SQL] arrays |