At 11:11 AM 2/11/02 -0500, Tom Lane wrote:
>Philip Warner <pjw@rhyme.com.au> writes:
>This strikes me as solving an entirely different issue
Well, a related issue: you are talking about (slightly) changing the
encoding of dumped data - why not therefor allow for an (optional) header
with full encoding details. Column headers are just a minor bonus.
>- with great
>loss of backwards compatibility.
Not if anything without the 'WITH HEADERS' is treated as per current.
Anyone having M$ problems can use the new format (and pg_dump could use it
always).
>the moment I'd like to keep this thread focused on the issue of coping
>with newline translations.
No big deal, but this seems to be an encoding issue; and it seems like a
good idea to formalize it somehow.
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \| | --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/