On 10/20/06, Jean-Christophe Roux <[EMAIL PROTECTED]> wrote:
Hello,
I have a table like this:
create table dummy (value integer primary key);
and I insert a row like this
insert into dummy values(0);
then I want to insert three rows:
insert into dummy values(0);
insert into dummy values(1);
insert into dummy values(2);
none of them will be inserted because the first insert is a primary key
violation. How can I have postgreSQL not mind about the error and proceed to
the next insert. I could send the inserts one at a time but bundling them
speeds up the process.
Thanks
if this is bulk insert,
1. insert into scratch table:
create temp table scratch_foo as select * from foo limit 0;
2. insert into scratch, etc.
3. insert into foo select distinct on * from scratch_foo <-- season to taste
merlin
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
