Re: Reset sequence to current maximum value of rows

From: Rich Shepard <rshepard(at)appl-ecosys(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Reset sequence to current maximum value of rows
Date: 2024-06-13 20:09:51
Message-ID: bcf7b38-857e-b44c-a0c5-71bfc1f52b9c@appl-ecosys.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, 13 Jun 2024, Ron Johnson wrote:

> No need to do that. Just write:
> INSERT INTO public.companies (company_name, , industry, status)
> VALUES ('Berkshire Hathaway', 'Conglomerate', 'Mumble');
>
> The next value of companies_org_nbr_seq will automatically be taken and
> inserted into the table.

Ron,

Aha! So it's likely that by listing the PK column name in the list of
columns to be inserted was what caused the problem? No need to specify
DEFAULT for it?

I'm writing a script to enter all contact within these companies. I'll leave
out 'person_nbr' in the list of columns and DEFAULT at the beginning of the
VALUES () section.

I didn't pick this up in my readings.

Thank you,

Rich

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David G. Johnston 2024-06-13 20:14:56 Re: Reset sequence to current maximum value of rows
Previous Message Rich Shepard 2024-06-13 19:57:19 Re: Reset sequence to current maximum value of rows