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

From David G. Johnston
Subject Re: Definging columns for INSERT statements
Date
Msg-id CAKFQuwbpWc97huJPbQSQ_F1JoEk+X_3KTbSDGdv+8ueUhktO+g@mail.gmail.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 Wed, Jun 12, 2024 at 2:11 PM Rich Shepard <rshepard@appl-ecosys.com> 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?

The whole point of the server is to parse text and tell you if it has syntax errors and then, if not, execute what you gave it.


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


Not sure where you got the idea that something besides a plain column name can appear in the optional parentheses after the table name.

David J.

pgsql-general by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: UPDATE with multiple WHERE conditions
Next
From: Rich Shepard
Date:
Subject: Re: UPDATE with multiple WHERE conditions