Date: Wed, 12 Jun 2024 16:24:56 -0700 (PDT)
From: Rich Shepard <rshepard@appl-ecosys.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: Definging columns for INSERT statements
In-Reply-To: <92fdd56a-9600-42d6-bee7-5f071f0f0f09@aklaver.com>
Message-ID: <61398511-e28d-f9bd-d44-33a69a1c55@appl-ecosys.com>
References: <27d9076-c416-7847-7bd-159a5c3ee38a@appl-ecosys.com> <92fdd56a-9600-42d6-bee7-5f071f0f0f09@aklaver.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://www.postgresql.org/message-id/61398511-e28d-f9bd-d44-33a69a1c55%40appl-ecosys.com>
Precedence: bulk

On Wed, 12 Jun 2024, Adrian Klaver wrote:

> Assuming 'people_person_nbr_seq' is the sequence attached to person_nbr
> and the other DEFAULTs are the column defaults then the syntax would be:
>
> INSERT INTO people
> (person_nbr, lname, fname, job_title, company_nbr,loc_nbr, direct_phone, 
> cell_phone,email, active)
> VALUES
> (DEFAULT, 'klaver', 'adrian', DEFAULT, 1, 1, '555-1234', '555-4321', 
> 'adrian.klaver@aklaver.com', DEFAULT);
>
> If they are not the column defaults then just supply the literal value.

Adrian,

No matter how many postgres docs and web pages I read I didn't find an
example as explicit as yours. Columns other than the person_nbr were not
defined with defaults and I expected to enter them for each row.

Many thanks for another valuable lesson.

Best regards,

Rich