Re: Should we support new definition for Identity column : GENERATED BY DEFAULT ON NULL?

From: Geoff Winkless <pgsqladmin(at)geoff(dot)dj>
To: David Fetter <david(at)fetter(dot)org>
Cc: Vik Fearing <vik(at)postgresfriends(dot)org>, Himanshu Upadhyaya <upadhyaya(dot)himanshu(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Should we support new definition for Identity column : GENERATED BY DEFAULT ON NULL?
Date: 2021-11-03 14:54:12
Message-ID: CAEzk6ffopCRUogpEq7FPKW3S9LX0+rEEHdy+NRPLsm6E9zJ6Qg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 3 Nov 2021 at 14:39, David Fetter <david(at)fetter(dot)org> wrote:

> Unfortunately, the PREPARE/EXECUTE infrastructure, and not just for
> PostgreSQL, has no way of passing along DEFAULT explicitly, i.e. it
>

My $.02: I'd be much happier with the idea of changing those
obviously-deficient interfaces to allow explicit DEFAULT than of having an
explicit NULL treated differently depending on the column type.

Geoff

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2021-11-03 15:06:34 Re: remove internal support in pgcrypto?
Previous Message Alexander Pyhalov 2021-11-03 14:50:19 Re: Partial aggregates pushdown