Date: Thu, 13 Jun 2024 11:24:37 -0700 (PDT)
From: Rich Shepard <rshepard@appl-ecosys.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: Reset sequence to current maximum value of rows
In-Reply-To: <CAKFQuwba=vb16vR47W0oo3SirkJ+UqLEg5j9-fqe+vm=0Q7_qw@mail.gmail.com>
Message-ID: <1b139d9a-b95f-f7c8-52fb-9d7442c69ad9@appl-ecosys.com>
References: <387fa6c2-5de-f24-d522-46282597703@appl-ecosys.com> <CAKFQuwba=vb16vR47W0oo3SirkJ+UqLEg5j9-fqe+vm=0Q7_qw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset=US-ASCII
Archived-At: <https://www.postgresql.org/message-id/1b139d9a-b95f-f7c8-52fb-9d7442c69ad9%40appl-ecosys.com>
Precedence: bulk

On Thu, 13 Jun 2024, David G. Johnston wrote:

> You need to show your work here.  As your PK is a number it cannot have a
> company name as a value and so this doesn't make sense.

David,

insert into companies (company_nbr,company_name,industry,status) values
(DEFAULT,'new company name','Industry','Opportunity')

With DEFAULT as the company_nbr why can't the company_name not have a value?

> It didn't...

I changed the company_name for all company_nbr using the 'new company name'
for all rows with 'Industry' in that column.

> And how to I reset sequences to ignore all current values
> This doesn't make sense...

Then I cannot use the sequence for adding new rows in the table and I must
manually enter each PK number?

> If you use the default when inserting the next value in the sequence is
> used.

Yes, that's the theory. It didn't work for me and why it didn't is what I
want to understand.

Regards,

Rich