ELEMENTS directive
Applies to ❌ Open Source Edition ✅ Express Edition ✅ Professional Edition ✅ Enterprise Edition
The ELEMENTS directive allows for generating XML elements for each column instead of attributes.
Consider the following query
SELECT id, title FROM book ORDER BY id FOR XML RAW, ELEMENTS
create.select(BOOK.ID, BOOK.TITLE)
.from(BOOK)
.orderBy(BOOK.ID)
.forXML().raw().elements()
.fetch();
This query produces a document like this:
<row><ID>1</ID><TITLE>1984</TITLE></row> <row><ID>2</ID><TITLE>Animal Farm</TITLE></row> <row><ID>3</ID><TITLE>O Alquimista</TITLE></row> <row><ID>4</ID><TITLE>Brida</TITLE></row>
Dialect support
This example using jOOQ:
select(BOOK.ID).from(BOOK).orderBy(BOOK.ID).forXML().raw().elements()
Translates to the following dialect specific expressions:
DB2, Oracle, Postgres
SELECT xmlagg(xmlelement( NAME row, xmlelement(NAME ID, ID) )) FROM ( SELECT BOOK.ID FROM BOOK ORDER BY BOOK.ID ) t
SQLServer
SELECT ( SELECT BOOK.ID FROM BOOK ORDER BY BOOK.ID FOR XML RAW, ELEMENTS )
Sybase
SELECT ( SELECT BOOK.ID FROM BOOK ORDER BY BOOK.ID FOR XML RAW, ELEMENTS ) FROM SYS.DUMMY
Teradata
SELECT xmlagg(xmlelement(
NAME row,
xmlelement(NAME ID, ID)
))
FROM (
SELECT *
FROM (
SELECT TOP 999999999999999999 BOOK.ID
FROM BOOK
ORDER BY BOOK.ID
) x
) t
ASE, Access, Aurora MySQL, Aurora Postgres, BigQuery, ClickHouse, CockroachDB, Databricks, Derby, DuckDB, Exasol, Firebird, H2, HSQLDB, Hana, Informix, MariaDB, MemSQL, MySQL, Redshift, SQLDataWarehouse, SQLite, Snowflake, Trino, Vertica, YugabyteDB
/* UNSUPPORTED */
Generated with jOOQ 3.21. Support in older jOOQ versions may differ. Translate your own SQL on our website
Feedback
Do you have any feedback about this page? We'd love to hear it!