From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | greg(at)turnstep(dot)com |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: XML ouput for psql |
Date: | 2003-03-05 22:37:35 |
Message-ID: | Pine.LNX.4.44.0303051829550.2224-100000@peter.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
greg(at)turnstep(dot)com writes:
> I think all psql needs is a simple output, similar to the ones used by
> Oracle, Sybase, and MySQL; the calling application should then process
> it in some way as needed (obviously this is not for interactive use).
> Where can one find a "standard table model?"
I think for processing-oriented output, the system described in the
SQL/XML standard draft is the way to go. Considering the people who wrote
it, it's probably pulled from, or bound to appear in, a major commercial
database.
I also think that psql is not the place to implement something like this.
It's most likely best put in the backend, as a function like
xmlfoo('select * from t1;')
Then any interface and application that likes it, not just psql-based
ones, can use it.
--
Peter Eisentraut peter_e(at)gmx(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2003-03-05 22:38:27 | Re: XML ouput for psql |
Previous Message | Tom Lane | 2003-03-05 21:53:20 | Re: [PATCHES] Non-colliding auto generated names |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2003-03-05 22:38:27 | Re: XML ouput for psql |
Previous Message | Tom Lane | 2003-03-05 21:53:20 | Re: [PATCHES] Non-colliding auto generated names |