From: Bryce Nesbitt <bryce1@obviously.com>
To: pgsql-sql@postgresql.org
Cc: Philip Hallstrom <postgresql@philip.pjkh.com>
Subject: Re: Seeking quick way to clone a row, but give it a new pk.
Date: Wed, 07 Feb 2007 23:19:46 -0800
Message-ID: <45CACF12.1060800@obviously.com> (raw)
In-Reply-To: <20070207181622.I3035@bravo.pjkh.com>
References: <45CA50E6.6090006@obviously.com>
<20070207181622.I3035@bravo.pjkh.com>
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/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: bryce1@obviously.com, postgresql@philip.pjkh.com
Subject: Re: Seeking quick way to clone a row, but give it a new pk.
In-Reply-To: <45CACF12.1060800@obviously.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox