I guess then I will switch to use COPY "tablename (fieldlist)" FROM. Will this end up being faster anyway.
In case anyone was wondering here is a good example of how to do it in php from: http://us4.php.net/manual/en/function.pg-put-line.php <?php $conn = pg_pconnect("dbname=foo"); pg_query($conn, "create table bar (a int4, b char(16), d float8)"); pg_query($conn, "copy bar from stdin"); pg_put_line($conn, "3\thello world\t4.5\n"); pg_put_line($conn, "4\tgoodbye world\t7.11\n"); pg_put_line($conn, "\\.\n"); pg_end_copy($conn); ?> thanks, Rick Gigger ----- Original Message ----- From: "Tom Lane" <[EMAIL PROTECTED]> To: "Rick Gigger" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, October 06, 2003 1:04 PM Subject: Re: [GENERAL] Possible bug on insert > "Rick Gigger" <[EMAIL PROTECTED]> writes: > > insert into bugtest (a) select '1' union select '1'; -- this one fails > > > Is this a bug? > > No. It's unfortunate perhaps, but it's not a bug. The UNION forces us > to make a decision about the output datatype of the UNION operation. > In your other cases the chosen datatype is integer, which can later be > cast to smallint for the insert, but in this case the chosen datatype is > text, which is not implicitly castable to smallint. > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 8: explain analyze is your friend > ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
