| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Emmanuel Cecchet <manu(at)asterdata(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: COPY enhancements |
| Date: | 2009-09-11 15:38:00 |
| Message-ID: | 4AAA6ED8.5090309@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>
>> I don't see any reasonable way to sandwhich the FORCE NOT NULL syntax
>> into a keyword/value notation.
>>
>
> Any number of ways, for example "force_not_null = true" or multiple
> occurrences of "force_not_null = column_name". Andrew was on the verge
> of admitting we don't need that option anymore anyway ;-), so I don't
> think we should allow it to drive an exception to the simplified syntax.
>
>
>
We won't need it if we can use an expression on the source, like
coalesce(t[4],"")
that gets applied on the way in. Until then it is useful, if ugly.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2009-09-11 15:43:32 | Re: RfD: more powerful "any" types |
| Previous Message | Tom Lane | 2009-09-11 15:37:33 | Re: COPY enhancements |