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

From Adrian Klaver
Subject Re: Definging columns for INSERT statements
Date
Msg-id 92fdd56a-9600-42d6-bee7-5f071f0f0f09@aklaver.com
Whole thread Raw
In response to 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 14:11, Rich Shepard wrote:
> I have > 100 rows to add to a table using INSERT INTO statements. I want 
> the
> PK to be the next value in the sequence. Would this be the appropriate
> syntax for the columns to be entered?
> 
> INSERT INTO people (person_nbr 
> DEFAULT('people_person_nbr_seq'),lname,fname,job_title DEFAULT 
> 'Contact',company_nbr,loc_nbr,direct_phone,cell_phone,email,active 
> DEFAULT('true')) VALUES
> ( ...

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.

> 
> TIA,
> 
> Rich
> 
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com




pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: PG16.1 security breach?
Next
From: "David G. Johnston"
Date:
Subject: Re: PG16.1 security breach?