| From: | Csaba Nagy <nagy(at)ecircle-ag(dot)com> |
|---|---|
| To: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
| Cc: | David Gardner <david(at)gardnerit(dot)net>, Postgres general mailing list <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Excell |
| Date: | 2007-06-21 15:01:19 |
| Message-ID: | 1182438079.26700.50.camel@coppola.muc.ecircle.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 2007-06-21 at 16:45, Scott Marlowe wrote:
> Another option is to use your favorite scripting language and throw an
> excel header then the data in tab delimited format. Or even in excel
> xml format.
Why would you need any scripting language ? COPY supports CSV output
pretty well, it can even put you a header on the top. And 8.2 can COPY a
SELECT too, so you can generate the CSV dump directly from joins too...
on older systems I usually create a temporary table as the result of the
join and then COPY that - plain SQL is all you need... I always did it
this way when it comes to occasional data from/to excel.
Now if it is about regularly exchanging data with excel, possibly using
excel as a DB interface, probably ODBC is the only viable choice, but if
the OP really needs a DB for the data, I would say using excel as the
interface to it is likely a bad decision...
Cheers,
Csaba.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Huxton | 2007-06-21 15:16:56 | Re: PostgreSQL question re select for update (locking??) |
| Previous Message | Richard Huxton | 2007-06-21 15:00:41 | Re: Aggregates |