Re: Seeking quick way to clone a row, but give it a new pk. - Mailing list pgsql-sql

From Bryce Nesbitt
Subject Re: Seeking quick way to clone a row, but give it a new pk.
Date
Msg-id 45CACF12.1060800@obviously.com
Whole thread Raw
In response to Re: Seeking quick way to clone a row, but give it a new pk.  (Philip Hallstrom <postgresql@philip.pjkh.com>)
Responses Re: Seeking quick way to clone a row, but give it a new pk.  (Achilleas Mantzios <achill@matrix.gatewaynet.com>)
Re: Seeking quick way to clone a row, but give it a new pk.  (Aarni Ruuhimäki <aarni@kymi.com>)
List pgsql-sql
Philip Hallstrom wrote:
>> I need to create some nearly identical copies of rows in a complicated
>> table.
>>
>> Is there a handy syntax that would let me copy a existing row, but get a
>> new primary key for the copy?  I'd then go in an edit the 1 or 2
>> additional columns that differ.  The duplicate would be in the same
>> table as the original.
>>
>> This would save me a bunch of typing.  Can it be done?
>
> INSERT INTO mytable SELECT * FROM mytable WHERE pk = 123;
>
> Or something close to that... I suspect if you changed the '*' to the
> columns you wanted you could also work in the other columns you want
> to change as well...
But that will violate the unique primary key constraint:

insert into xx_plan_rule select * from xx_plan_rule where rule_id=9;
ERROR:  duplicate key violates unique constraint "xx_plan_rule_pkey"


-- 
----
Visit http://www.obviously.com/



pgsql-sql by date:

Previous
From: Bryce Nesbitt
Date:
Subject: Re: Seeking quick way to clone a row, but give it a new pk.
Next
From: Achilleas Mantzios
Date:
Subject: Re: Seeking quick way to clone a row, but give it a new pk.