| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Emmanuel Cecchet <manu(at)asterdata(dot)com> |
| Cc: | Emmanuel Cecchet <Emmanuel(dot)Cecchet(at)asterdata(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: generic copy options |
| Date: | 2009-09-20 18:01:14 |
| Message-ID: | 24564.1253469674@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Emmanuel Cecchet <manu(at)asterdata(dot)com> writes:
> Here you will force every format to use the same set of options
How does this "force" any such thing?
> and if
> someone introduces a new option, you will have to modify all other
> formats to make sure they throw an error telling the user that this
> option is not supported.
Well, if we do it your way then we will instead need a collection of
code to throw errors for combinations like (xml on, csv_header on).
I don't really see any improvement there.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Emmanuel Cecchet | 2009-09-20 18:25:01 | Re: generic copy options |
| Previous Message | Emmanuel Cecchet | 2009-09-20 17:53:18 | Re: generic copy options |