Skip site navigation (1) Skip section navigation (2)

Re: Plan for CSV handling of quotes, NULL

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: pgsql-patches(at)postgresql(dot)org
Subject: Re: Plan for CSV handling of quotes, NULL
Date: 2004-04-15 14:17:36
Message-ID: 407E9980.2020306@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-patches
Bruce Momjian wrote:

>What about NULL input?  Is my warning and promotion to zero-length
>string for NOT NULL columns OK?
>
>  
>


I know I originally floated this idea or one very like it, but I have 
become convinced it is not a good idea after all. The user might not 
know or expect that the data file has nulls, in which case promoting the 
value might not be what s/he expects at all. I think there's a world of 
difference between the user saying "I know there might be nulls in this 
CSV column - ignore them" and us doing it automagically and issuing a 
warning, which might elicit the response "Doh! I wish you'd told me 
beforehand." If we provide an option to override handling of nulls on 
input per column, then we can safely fail on encountering an unexpected 
null, and all the user will have to do would be to rerun the command 
with the override. Recovering from an unexpected promotion to non-null 
would be a lot harder.

cheers

andrew


Responses

pgsql-patches by date

Next:From: Andrew DunstanDate: 2004-04-15 14:29:01
Subject: Re: Plan for CSV handling of quotes, NULL
Previous:From: Bruce MomjianDate: 2004-04-15 14:17:27
Subject: Re: Plan for CSV handling of quotes, NULL

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group