Re: [HACKERS] Output filter for psql

2009-01-28 Thread Andrew Dunstan
D'Arcy J.M. Cain wrote: On Wed, 28 Jan 2009 14:08:54 -0500 Andrew Dunstan wrote: D'Arcy J.M. Cain wrote: I suppose we could define another line with options that we could define for meta information such as the border setting and the table name and whatever we define later. E.g: "t

Re: [HACKERS] Output filter for psql

2009-01-28 Thread D'Arcy J.M. Cain
On Wed, 28 Jan 2009 14:08:54 -0500 Andrew Dunstan wrote: > D'Arcy J.M. Cain wrote: > > I suppose we could define another line with options that we could > > define for meta information such as the border setting and the table > > name and whatever we define later. E.g: > > > > "table:person","bor

Re: [HACKERS] Output filter for psql

2009-01-28 Thread Andrew Dunstan
D'Arcy J.M. Cain wrote: On Thu, 8 Jan 2009 17:22:04 -0500 "D'Arcy J.M. Cain" wrote: So, I guess psql should pass XML to the user's filter and simply dump its output to the screen. Is XML the best format? It would allow us to pass meta information. For example, we could pass the border s

Re: [HACKERS] Output filter for psql

2009-01-28 Thread D'Arcy J.M. Cain
On Thu, 8 Jan 2009 17:22:04 -0500 "D'Arcy J.M. Cain" wrote: > So, I guess psql should pass XML to the user's filter and simply dump > its output to the screen. Is XML the best format? It would allow us > to pass meta information. For example, we could pass the border > setting so that the filte

[HACKERS] Output filter for psql

2009-01-08 Thread D'Arcy J.M. Cain
I have mentioned this as a side issue in another thread. I thought that it would be useful to start a separate thread for this. Perhaps this won't be so difficult to code and we can forget all about the ReST discussion. So, I guess psql should pass XML to the user's filter and simply dump its ou