From: | Michael Glaesemann <grzm(at)seespotcode(dot)net> |
---|---|
To: | Peter <peter(at)greatnowhere(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Insert/select union bug |
Date: | 2006-09-27 11:55:29 |
Message-ID: | 367229F1-E589-4386-890F-5C3F84008709@seespotcode.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sep 27, 2006, at 20:39 , Peter wrote:
>> Using COPY avoids this issue ofcourse, because there's a direct
>> link to the table. Similarly, as of 8.2 it will be possible to do:
>> INSERT INTO table (blah) VALUES (x,y,a),(f,d,g),(s,f,g), etc...
>> Which will also avoid the issue.
> COPY wont work... my list of columns for insert is also dynamically
> built and will never cover all fields in table.
How about doing the two-step? Create a temp table with the columns
you're going to load, COPY into the temp table, and do a INSERT INTO
table (...) SELECT ... FROM temp_table?
Michael Glaesemann
grzm seespotcode net
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2006-09-27 12:23:39 | Re: Insert/select union bug |
Previous Message | Peter | 2006-09-27 11:39:13 | Re: Insert/select union bug |