From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Gregory Stark <stark(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCHES] allow CSV quote in NULL |
Date: | 2007-07-27 19:19:17 |
Message-ID: | 20070727191917.GL4887@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
* Andrew Dunstan (andrew(at)dunslane(dot)net) wrote:
> Stephen Frost wrote:
>> I'm honestly not a big fan of the "columnlist" approach that's been
>> taken with the options. While I understand the desire to seperate the
>> parsing from the typing, making the users essentially do that association
>> for us by way of making them specify how to handle each column explicitly
>> is worse than just accepting that different types may need to be handled
>> in different ways.
>>
>
> Whether or not you like it, the fact is it's there. I think any solution
> should be consistent with what is done.
Other, unrelated, options being or not being there doesn't really have
any bearing on this though. I'm not inventing new syntax here. I'm
just removing a restriction on what the user can do that doesn't need
to exist. Indeed, other more convoluted and complex things could still
be added, if someone wants them, this doesn't prevent that.
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2007-07-27 20:29:01 | Re: Updated tsearch documentation |
Previous Message | Andrew Dunstan | 2007-07-27 18:26:26 | Re: [PATCHES] allow CSV quote in NULL |
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2007-07-27 20:01:06 | Re: [PATCHES] patch win32.mak of libpq |
Previous Message | Andrew Dunstan | 2007-07-27 18:26:26 | Re: [PATCHES] allow CSV quote in NULL |