Re: [PATCHES] allow CSV quote in NULL

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: 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 18:26:26
Message-ID: 46AA38D2.4070908@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

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.

When CSV was first discussed we looked at doing type-specific behaviour.
The end of the long debate was that we simply couldn't do that safely,
and the only recourse was to require the user to specify the behaviour
required if it differed from the default. You might be inclined to want
to revisit that, but I am not.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2007-07-27 19:19:17 Re: [PATCHES] allow CSV quote in NULL
Previous Message Stuart 2007-07-27 18:22:04 ascii() for utf8

Browse pgsql-patches by date

  From Date Subject
Next Message Stephen Frost 2007-07-27 19:19:17 Re: [PATCHES] allow CSV quote in NULL
Previous Message Stephen Frost 2007-07-27 18:09:52 Re: [PATCHES] allow CSV quote in NULL