From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Steve Atkins <steve(at)blighty(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: CSV mode option for pg_dump |
Date: | 2006-06-13 16:47:36 |
Message-ID: | 448EEC28.1070602@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>
> Would that be adequate, or do we really want to reimplement and maintain
> all
> the output format complexity in our own code, in C?
I think the point is that we should provide a native implementation
because not everyone is crazy enough to use perl (blatant jab ;)). I
would never expect a customer to write a perl or python script just to
get their data in what is widely considered a standard business format
that can be imported by their userland application.
The people on the hackers list, are NOT the target for this feature. The
people on general, admin and novice are.
Sincerely,
Joshua D. Drake
>
> Cheers,
> Steve
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Bill Bartlett | 2006-06-13 16:51:22 | Re: CSV mode option for pg_dump |
Previous Message | A.M. | 2006-06-13 16:45:01 | Re: Fabian Pascal and RDBMS deficiencies in fully |