Re: multiline CSV fields

Tom Lane wrote:

>Andrew Dunstan  writes:
>  
>
>>+ 		if (!embedded_line_warning  && (c == '\n' || c == '\r') )
>>+ 		{
>>+ 			embedded_line_warning = true;
>>+ 			elog(WARNING,
>>+ 				 "CSV fields with embedded linefeed or carriage return "
>>+ 				 "characters might not be able to be reimported");
>>+ 		}
>>    
>>
>
>What about forcibly translating them to the two-character sequences \n
>or \r?  Or is that not considered a CSV-compatible representation?
>
>
>  
>

Not compatible AFAIK. Certainly not portably. And the warning would 
still be true, because we don't do this unescaping on the way back in. I 
think the way the comment in the patch suggests and previous emails have 
discussed is the right way to go with this - I will attend to it after 
we branch ;-)

cheers

andrew