| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, James Coleman <jtc331(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Should we document how column DEFAULT expressions work? |
| Date: | 2024-07-05 22:43:44 |
| Message-ID: | CAApHDvoirShaLmpwtqjnKfBUvWGoqSfcSSdEUK9nCkMWzujM+A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2 Jul 2024 at 13:48, David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
>
> On Tue, 2 Jul 2024 at 02:43, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > I'd be more excited about this discussion if I didn't think that
> > the chances of removing 'now'::timestamp are exactly zero. You
> > can't just delete useful decades-old features, whether there's
> > a better way or not.
>
> Do you have any thoughts on rejecting trailing punctuation with the
> timestamp special values?
Cancel that idea. I'd thought that these special values must be
standalone, but I didn't realise until a few minutes ago that it's
perfectly valid to mix them:
select 'yesterday 13:00:00'::timestamp, 'yesterday allballs'::timestamp;
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Erik Wienhold | 2024-07-05 23:42:48 | Re: CREATE OR REPLACE MATERIALIZED VIEW |
| Previous Message | David G. Johnston | 2024-07-05 22:00:07 | Re: Should we document how column DEFAULT expressions work? |