* Tom Lane <[EMAIL PROTECTED]> [010430 08:37] wrote:
> Alfred Perlstein <[EMAIL PROTECTED]> writes:
> > It would be very helpful if the COPY command could be expanded
> > in order to provide positional parameters.
>
> I think it's a bad idea to try to expand COPY into a full-tilt data
> import/conversion utility, which is the direction that this sort of
> suggestion is headed in. COPY is designed as a simple, fast, reliable,
> low-overhead data transfer mechanism for backup and restore. The more
> warts we add to it, the less well it will serve that purpose.
Honestly it would be hard for COPY to be any more less serving of
people's needs, it really makes sense for it to be able to parse
positional paramters for both speed and correctness.
> Example: if we allow selective column import, what do we do with missing
> columns?
What is already done, if you initiate a copy into a 5 column table
using only 4 columns of copy data the fifth is left empty.
> Must COPY now be able to handle insertion of default-value
> expressions?
No, copy should be what it is simple but at the same time useful
enough for bulk transfer without painful contortions and fear
of modifying tables.
--
-Alfred Perlstein - [[EMAIL PROTECTED]]
Represent yourself, show up at BABUG http://www.babug.org/
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://www.postgresql.org/search.mpl
