On 2/16/24 10:10 AM, David G. Johnston wrote:
On Fri, Feb 16, 2024 at 10:24 AM Michael Corey
wrote:
By explicitly making a column an IDENTITY column it is going to
make a sequence behind the scenes even if one with a similar name
exists. I tried and it created part_tab_part_id_se
On Fri, Feb 16, 2024 at 10:24 AM Michael Corey
wrote:
> By explicitly making a column an IDENTITY column it is going to make a
> sequence behind the scenes even if one with a similar name exists. I tried
> and it created part_tab_part_id_seq1. Is there no way to have it use the
> original part_
By explicitly making a column an IDENTITY column it is going to make a
sequence behind the scenes even if one with a similar name exists. I tried
and it created part_tab_part_id_seq1. Is there no way to have it use the
original part_tab_part_id_seq? How do I get the data and the sequence in
sync
On Fri, Feb 16, 2024 at 9:24 AM Michael Corey
wrote:
> If I run these two statements I get an error
> ERROR: relation "part_tab_part_id_seq" already exists
>
> I tried different combinations of this ALTER TABLE statement and none seem
> to work. What is the proper way to reattach the identity a
What is the proper way to deal with identity columns on a table
rebuild/partitioning? If I have the following non-partitioned table
CREATE TABLE IF NOT EXISTS part_tab
(
part_id bigint NOT NULL GENERATED BY DEFAULT AS IDENTITY ( INCREMENT 1
START 0 MINVALUE 0 MAXVALUE 9223372036854775807 CACH
