Re: support virtual generated column not null constraint - Mailing list pgsql-hackers

From Navneet Kumar
Subject Re: support virtual generated column not null constraint
Date
Msg-id CANzA6sqsVeN-p8dqtM7v4376neOE74CDLfZKwvWG7zb7a+btZQ@mail.gmail.com
Whole thread Raw
In response to Re: support virtual generated column not null constraint  (Navneet Kumar <thanit3111@gmail.com>)
List pgsql-hackers


This scenario fails
1. CREATE TABLE person (
    id INT GENERATED BY DEFAULT AS IDENTITY,
    first_name VARCHAR(50) NOT NULL,
    last_name VARCHAR(50) NOT NULL
);

2. INSERT INTO person (first_name, last_name)
VALUES ('first', 'last');

3. ALTER TABLE person
ADD COLUMN full_name VARCHAR(100) GENERATED ALWAYS AS (first_name || ' ' || last_name) VIRTUAL;

Forgot to mention NOT NULL constraint in above query.

3. ALTER TABLE person
ADD COLUMN full_name VARCHAR(100) NOT NULL GENERATED ALWAYS AS (first_name || ' ' || last_name) VIRTUAL;

ERROR:  column "full_name" of relation "person" contains null values
 

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Commitfest app release on Feb 17 with many improvements
Next
From: Álvaro Herrera
Date:
Subject: Re: pgsql: reindexdb: Add the index-level REINDEX with multiple jobs