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

From: Vik Fearing <vik(at)postgresfriends(dot)org>
To: 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 10:07:58
Message-ID: 228a6c8f-694e-7550-67bf-ce6e6dafb2c4@postgresfriends.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 11/2/21 12:19 PM, Himanshu Upadhyaya wrote:
> Hi,
>
> Trying to insert NULL value to the Identity column defined by "GENERATED BY
> DEFAULT" is disallowed, but there can be use cases where the user would
> like to have an identity column where manual NULL insertion is required(and
> it should not error-out by Postgres).

What could possibly be the use case for this?

> Thoughts?

I don't like it.
--
Vik Fearing

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2021-11-03 10:13:30 Re: Data is copied twice when specifying both child and parent table in publication
Previous Message Andrey Borodin 2021-11-03 09:32:51 Re: lastOverflowedXid does not handle transaction ID wraparound