gsoc ideas

From: longlong <asfnuts(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: gsoc ideas
Date: 2008-03-10 05:10:45
Message-ID: d9f0a46b0803092210p76d12611j5b2dac49d468a9cf@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

hi,all.

i want some advice about ideas for gsoc. i don't konw if it is appropriate
that i send a email here, so if you feel uncomfortable, please accept my
apology.

1.release8.2 make COPY TO can copy the output of an arbitrary SELECT
statement. so i think maybe COPY FROM can get data from output and 'insert
into' some column that designated. the format of the command will be
discussed.

2.this come from TODO list: COPY always behaviors like a unit of work thar
consists of some insert commands, if any error, it rollback. but sometimes
we only care the data should be inserted. in that situation, i used to use
"try....catch...." insert row by row to skip the error, because it will take
much time to examine every row. so:
Allow COPY to report error lines and continue.
this is a good idea.

3.sometimes, i want to copy data from one database to another. i think using
COPY will simple the code. i want the content from COPY TO not store in the
file, but in the memory, and i can COPY FROM the memory(i don't kown COPY
with STDIN and STDOUT can do this or not.).

how do you think of these ideas?

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Christian Teguh 2008-03-10 06:43:03 PostreSQL Single File ( Like M$ Access)
Previous Message postgre 2008-03-09 23:39:15 large object import