Re: Nasty, propagating POLA violation in COPY CSV HEADER

From: "Marc Mamin" <M(dot)Mamin(at)intershop(dot)de>
To: "Josh Berkus" <josh(at)agliodbs(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Nasty, propagating POLA violation in COPY CSV HEADER
Date: 2012-06-20 17:35:25
Message-ID: C4DAC901169B624F933534A26ED7DF310F96B014@JENMAIL01.ad.intershop.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> -----Ursprüngliche Nachricht-----
> Von: pgsql-hackers-owner(at)postgresql(dot)org im Auftrag von Josh Berkus
> Gesendet: Mi 6/20/2012 7:06
> An: pgsql-hackers(at)postgresql(dot)org
> Betreff: Re: [HACKERS] Nasty, propagating POLA violation in COPY CSV HEADER

...

> (1) is valuable
> for backwards compatibility, and for cases where the CSV header was
> generated by another program (Excel?) so the column names don't match.

4) MAP_HEADER ('column 1'-> 'col_1', 'Date' -> 'input_date' ...)

to cover the case when column names do not match.

my 2 pences,

Marc Mamin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2012-06-20 17:35:33 Re: sortsupport for text
Previous Message Robert Haas 2012-06-20 17:17:57 Re: [PATCH 10/16] Introduce the concept that wal has a 'origin' node