Tommy Gildseth wrote:
> How do you define the table name when fetching data using a join,
> union etc. where the data doesn't necessarily originate from a single
> table?
If you use the query_to_xml function, then I just write ""
without any particular name.
> Another neat feature would be if yo
Peter Eisentraut wrote:
tableforest = false gives you something like
...
tableforest = true gives you something like
...
...
...
How do you define the table name when fetching data using a join, union
etc. where the data doesn't necessarily originate from a single table?
Could
Andrew Dunstan wrote:
> . table_to_xml_and_xmlschema seems like a mouthful - can we shorten
> it a bit?
Well, it gives you back a mouthful of data, too. :)
> . what are the two ways of representing data that tableforest
> distinguishes?
tableforest = false gives you something like
data
Peter Eisentraut wrote:
Here are the proposed signatures for the XML export functions.
While I have seen the output formats in use elsewhere, I could not find
any useful information on how to invoke these mappings, so the
following is purely my own invention.
table_to_xml(tbl regclass, nulls
Here are the proposed signatures for the XML export functions.
While I have seen the output formats in use elsewhere, I could not find
any useful information on how to invoke these mappings, so the
following is purely my own invention.
table_to_xml(tbl regclass, nulls boolean, tableforest boolean
