Re: Definging columns for INSERT statements - Mailing list pgsql-general

From Adrian Klaver
Subject Re: Definging columns for INSERT statements
Date
Msg-id 9288042e-9cd3-4121-ab99-459f0fac9f53@aklaver.com
Whole thread Raw
In response to Re: Definging columns for INSERT statements  (Rich Shepard <rshepard@appl-ecosys.com>)
Responses Re: Definging columns for INSERT statements
List pgsql-general
On 6/12/24 16:24, Rich Shepard wrote:
> 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.

The 'Examples' section at the bottom of this page:

https://www.postgresql.org/docs/current/sql-insert.html

is a useful resource.

> 
> Many thanks for another valuable lesson.
> 
> Best regards,
> 
> Rich
> 
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com




pgsql-general by date:

Previous
From: Rich Shepard
Date:
Subject: Re: Definging columns for INSERT statements
Next
From: Dragan Milivojević
Date:
Subject: Is NVMe RAID useless (performance-wise) with PostgreSQL?