-----BEGIN PGP SIGNED MESSAGE-----
> 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
Do you have a link to the exact section? I've found conflicting versions
of what constitutes the "standard" for xml output of SQL data.
> 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.
I think that is a good long-term solution, but I still think we need
to address the TODO item in the short run, and allow for a simple
reformatting of the query results from psql. If not, we should remove
that TODO item form psql and add a different one to the backend section.
Greg Sabino Mullane greg(at)turnstep(dot)com
PGP Key: 0x14964AC8 200303061020
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2003-03-06 15:35:59|
|Subject: Re: ETA for PostgreSQL 7.3.3? |
|Previous:||From: greg||Date: 2003-03-06 15:23:39|
|Subject: Re: Who puts the Windows binaries on the FTP server?|
pgsql-patches by date
|Next:||From: Bruce Momjian||Date: 2003-03-06 19:01:36|
|Subject: Re: performance: use pread instead of lseek+read|
|Previous:||From: Bruce Momjian||Date: 2003-03-06 02:30:28|
|Subject: Re: [PATCHES] Non-colliding auto generated names|