aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/xml.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2008-10-14 00:41:35 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2008-10-14 00:41:35 +0000
commit06224652f23441588b9d50cab7311e2c6ec05414 (patch)
tree7b7265a293be65b10a6a03d8b4ff9b789650be2d /src/backend/utils/adt/xml.c
parent1f238e569acbc2a41be497d4fe1b1b797e5ae902 (diff)
downloadpostgresql-06224652f23441588b9d50cab7311e2c6ec05414.tar.gz
postgresql-06224652f23441588b9d50cab7311e2c6ec05414.zip
Add docs and regression test about sorting the output of a recursive query in
depth-first search order. Upon close reading of SQL:2008, it seems that the spec's SEARCH DEPTH FIRST and SEARCH BREADTH FIRST options do not actually guarantee any particular result order: what they do is provide a constructed column that the user can then sort on in the outer query. So this is actually just as much functionality ...
Diffstat (limited to 'src/backend/utils/adt/xml.c')
0 files changed, 0 insertions, 0 deletions