github/jooq
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[#7908] Add documentation about UPDATE .. FROM

Browse Source
This commit is contained in:
lukaseder 2018-10-02 13:11:57 +02:00
parent 9cde8a76a4
commit 89bf328a89
10 changed files with 231 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
jOOQ-manual/src/main/resources/org/jooq/web/manual-3.10.xml
View File

@ -6134,6 +6134,29 @@ create.insertInto(AUTHOR, AUTHOR.FIRST_NAME, AUTHOR.LAST_NAME)
The above row value expressions usages are completely typesafe.
</p>
<h3>UPDATE .. FROM</h3>
<p>
Some databases, including PostgreSQL and SQL Server, support joining additional tables to an <code>UPDATE</code> statement using a vendor-specific <code>FROM</code> clause. This is supported as well by jOOQ:
</p>
</html><code-pair>
<sql><![CDATA[UPDATE BOOK_ARCHIVE
SET
BOOK_ARCHIVE.TITLE = BOOK.TITLE
FROM BOOK
WHERE BOOK_ARCHIVE.ID = BOOK.ID]]></sql>
<java><![CDATA[create.update(BOOK_ARCHIVE)
.set(BOOK_ARCHIVE.TITLE, BOOK.TITLE)
.from(BOOK)
.where(BOOK_ARCHIVE.ID.eq(BOOK.ID))
.execute();]]></java>
</code-pair><html>
<p>
In many cases, such a joined update statement can be emulated using a correlated subquery, or using updatable views.
</p>
<h3>UPDATE .. RETURNING</h3>
<p>
The Firebird and Postgres databases support a <code>RETURNING</code> clause on their <code>UPDATE</code> statements, similar as the <code>RETURNING</code> clause in <reference id="insert-statement" title="INSERT statements"/>. This is useful to fetch trigger-generated values in one go. An example is given here:

23
jOOQ-manual/src/main/resources/org/jooq/web/manual-3.11.xml
View File

@ -6278,6 +6278,29 @@ create.insertInto(AUTHOR, AUTHOR.FIRST_NAME, AUTHOR.LAST_NAME)
The above row value expressions usages are completely typesafe.
</p>
<h3>UPDATE .. FROM</h3>
<p>
Some databases, including PostgreSQL and SQL Server, support joining additional tables to an <code>UPDATE</code> statement using a vendor-specific <code>FROM</code> clause. This is supported as well by jOOQ:
</p>
</html><code-pair>
<sql><![CDATA[UPDATE BOOK_ARCHIVE
SET
BOOK_ARCHIVE.TITLE = BOOK.TITLE
FROM BOOK
WHERE BOOK_ARCHIVE.ID = BOOK.ID]]></sql>
<java><![CDATA[create.update(BOOK_ARCHIVE)
.set(BOOK_ARCHIVE.TITLE, BOOK.TITLE)
.from(BOOK)
.where(BOOK_ARCHIVE.ID.eq(BOOK.ID))
.execute();]]></java>
</code-pair><html>
<p>
In many cases, such a joined update statement can be emulated using a correlated subquery, or using updatable views.
</p>
<h3>UPDATE .. RETURNING</h3>
<p>
The Firebird and Postgres databases support a <code>RETURNING</code> clause on their <code>UPDATE</code> statements, similar as the <code>RETURNING</code> clause in <reference id="insert-statement" title="INSERT statements"/>. This is useful to fetch trigger-generated values in one go. An example is given here:

24
jOOQ-manual/src/main/resources/org/jooq/web/manual-3.12.xml
View File

@ -6320,6 +6320,30 @@ create.insertInto(AUTHOR, AUTHOR.FIRST_NAME, AUTHOR.LAST_NAME)
The above row value expressions usages are completely typesafe.
</p>
<h3>UPDATE .. FROM</h3>
<p>
Some databases, including PostgreSQL and SQL Server, support joining additional tables to an <code>UPDATE</code> statement using a vendor-specific <code>FROM</code> clause. This is supported as well by jOOQ:
</p>
</html><code-pair>
<sql><![CDATA[UPDATE BOOK_ARCHIVE
SET
BOOK_ARCHIVE.TITLE = BOOK.TITLE
FROM BOOK
WHERE BOOK_ARCHIVE.ID = BOOK.ID]]></sql>
<java><![CDATA[create.update(BOOK_ARCHIVE)
.set(BOOK_ARCHIVE.TITLE, BOOK.TITLE)
.from(BOOK)
.where(BOOK_ARCHIVE.ID.eq(BOOK.ID))
.execute();]]></java>
</code-pair><html>
<p>
In many cases, such a joined update statement can be emulated using a correlated subquery, or using updatable views.
</p>
<h3>UPDATE .. RETURNING</h3>
<p>
The Firebird and Postgres databases support a <code>RETURNING</code> clause on their <code>UPDATE</code> statements, similar as the <code>RETURNING</code> clause in <reference id="insert-statement" title="INSERT statements"/>. This is useful to fetch trigger-generated values in one go. An example is given here:

23
jOOQ-manual/src/main/resources/org/jooq/web/manual-3.3.xml
View File

@ -4537,6 +4537,29 @@ create.insertInto(AUTHOR, AUTHOR.FIRST_NAME, AUTHOR.LAST_NAME)
The above row value expressions usages are completely typesafe.
</p>
<h3>UPDATE .. FROM</h3>
<p>
Some databases, including PostgreSQL and SQL Server, support joining additional tables to an <code>UPDATE</code> statement using a vendor-specific <code>FROM</code> clause. This is supported as well by jOOQ:
</p>
</html><code-pair>
<sql><![CDATA[UPDATE BOOK_ARCHIVE
SET
BOOK_ARCHIVE.TITLE = BOOK.TITLE
FROM BOOK
WHERE BOOK_ARCHIVE.ID = BOOK.ID]]></sql>
<java><![CDATA[create.update(BOOK_ARCHIVE)
.set(BOOK_ARCHIVE.TITLE, BOOK.TITLE)
.from(BOOK)
.where(BOOK_ARCHIVE.ID.eq(BOOK.ID))
.execute();]]></java>
</code-pair><html>
<p>
In many cases, such a joined update statement can be emulated using a correlated subquery, or using updatable views.
</p>
<h3>UPDATE .. RETURNING</h3>
<p>
The Firebird and Postgres databases support a <code>RETURNING</code> clause on their <code>UPDATE</code> statements, similar as the <code>RETURNING</code> clause in <reference id="insert-statement" title="INSERT statements"/>. This is useful to fetch trigger-generated values in one go. An example is given here:

23
jOOQ-manual/src/main/resources/org/jooq/web/manual-3.4.xml
View File

@ -5329,6 +5329,29 @@ create.insertInto(AUTHOR, AUTHOR.FIRST_NAME, AUTHOR.LAST_NAME)
The above row value expressions usages are completely typesafe.
</p>
<h3>UPDATE .. FROM</h3>
<p>
Some databases, including PostgreSQL and SQL Server, support joining additional tables to an <code>UPDATE</code> statement using a vendor-specific <code>FROM</code> clause. This is supported as well by jOOQ:
</p>
</html><code-pair>
<sql><![CDATA[UPDATE BOOK_ARCHIVE
SET
BOOK_ARCHIVE.TITLE = BOOK.TITLE
FROM BOOK
WHERE BOOK_ARCHIVE.ID = BOOK.ID]]></sql>
<java><![CDATA[create.update(BOOK_ARCHIVE)
.set(BOOK_ARCHIVE.TITLE, BOOK.TITLE)
.from(BOOK)
.where(BOOK_ARCHIVE.ID.eq(BOOK.ID))
.execute();]]></java>
</code-pair><html>
<p>
In many cases, such a joined update statement can be emulated using a correlated subquery, or using updatable views.
</p>
<h3>UPDATE .. RETURNING</h3>
<p>
The Firebird and Postgres databases support a <code>RETURNING</code> clause on their <code>UPDATE</code> statements, similar as the <code>RETURNING</code> clause in <reference id="insert-statement" title="INSERT statements"/>. This is useful to fetch trigger-generated values in one go. An example is given here:

23
jOOQ-manual/src/main/resources/org/jooq/web/manual-3.5.xml
View File

@ -5554,6 +5554,29 @@ create.insertInto(AUTHOR, AUTHOR.FIRST_NAME, AUTHOR.LAST_NAME)
The above row value expressions usages are completely typesafe.
</p>
<h3>UPDATE .. FROM</h3>
<p>
Some databases, including PostgreSQL and SQL Server, support joining additional tables to an <code>UPDATE</code> statement using a vendor-specific <code>FROM</code> clause. This is supported as well by jOOQ:
</p>
</html><code-pair>
<sql><![CDATA[UPDATE BOOK_ARCHIVE
SET
BOOK_ARCHIVE.TITLE = BOOK.TITLE
FROM BOOK
WHERE BOOK_ARCHIVE.ID = BOOK.ID]]></sql>
<java><![CDATA[create.update(BOOK_ARCHIVE)
.set(BOOK_ARCHIVE.TITLE, BOOK.TITLE)
.from(BOOK)
.where(BOOK_ARCHIVE.ID.eq(BOOK.ID))
.execute();]]></java>
</code-pair><html>
<p>
In many cases, such a joined update statement can be emulated using a correlated subquery, or using updatable views.
</p>
<h3>UPDATE .. RETURNING</h3>
<p>
The Firebird and Postgres databases support a <code>RETURNING</code> clause on their <code>UPDATE</code> statements, similar as the <code>RETURNING</code> clause in <reference id="insert-statement" title="INSERT statements"/>. This is useful to fetch trigger-generated values in one go. An example is given here:

23
jOOQ-manual/src/main/resources/org/jooq/web/manual-3.6.xml
View File

@ -5636,6 +5636,29 @@ create.insertInto(AUTHOR, AUTHOR.FIRST_NAME, AUTHOR.LAST_NAME)
The above row value expressions usages are completely typesafe.
</p>
<h3>UPDATE .. FROM</h3>
<p>
Some databases, including PostgreSQL and SQL Server, support joining additional tables to an <code>UPDATE</code> statement using a vendor-specific <code>FROM</code> clause. This is supported as well by jOOQ:
</p>
</html><code-pair>
<sql><![CDATA[UPDATE BOOK_ARCHIVE
SET
BOOK_ARCHIVE.TITLE = BOOK.TITLE
FROM BOOK
WHERE BOOK_ARCHIVE.ID = BOOK.ID]]></sql>
<java><![CDATA[create.update(BOOK_ARCHIVE)
.set(BOOK_ARCHIVE.TITLE, BOOK.TITLE)
.from(BOOK)
.where(BOOK_ARCHIVE.ID.eq(BOOK.ID))
.execute();]]></java>
</code-pair><html>
<p>
In many cases, such a joined update statement can be emulated using a correlated subquery, or using updatable views.
</p>
<h3>UPDATE .. RETURNING</h3>
<p>
The Firebird and Postgres databases support a <code>RETURNING</code> clause on their <code>UPDATE</code> statements, similar as the <code>RETURNING</code> clause in <reference id="insert-statement" title="INSERT statements"/>. This is useful to fetch trigger-generated values in one go. An example is given here:

23
jOOQ-manual/src/main/resources/org/jooq/web/manual-3.7.xml
View File

@ -5879,6 +5879,29 @@ create.insertInto(AUTHOR, AUTHOR.FIRST_NAME, AUTHOR.LAST_NAME)
The above row value expressions usages are completely typesafe.
</p>
<h3>UPDATE .. FROM</h3>
<p>
Some databases, including PostgreSQL and SQL Server, support joining additional tables to an <code>UPDATE</code> statement using a vendor-specific <code>FROM</code> clause. This is supported as well by jOOQ:
</p>
</html><code-pair>
<sql><![CDATA[UPDATE BOOK_ARCHIVE
SET
BOOK_ARCHIVE.TITLE = BOOK.TITLE
FROM BOOK
WHERE BOOK_ARCHIVE.ID = BOOK.ID]]></sql>
<java><![CDATA[create.update(BOOK_ARCHIVE)
.set(BOOK_ARCHIVE.TITLE, BOOK.TITLE)
.from(BOOK)
.where(BOOK_ARCHIVE.ID.eq(BOOK.ID))
.execute();]]></java>
</code-pair><html>
<p>
In many cases, such a joined update statement can be emulated using a correlated subquery, or using updatable views.
</p>
<h3>UPDATE .. RETURNING</h3>
<p>
The Firebird and Postgres databases support a <code>RETURNING</code> clause on their <code>UPDATE</code> statements, similar as the <code>RETURNING</code> clause in <reference id="insert-statement" title="INSERT statements"/>. This is useful to fetch trigger-generated values in one go. An example is given here:

23
jOOQ-manual/src/main/resources/org/jooq/web/manual-3.8.xml
View File

@ -6005,6 +6005,29 @@ create.insertInto(AUTHOR, AUTHOR.FIRST_NAME, AUTHOR.LAST_NAME)
The above row value expressions usages are completely typesafe.
</p>
<h3>UPDATE .. FROM</h3>
<p>
Some databases, including PostgreSQL and SQL Server, support joining additional tables to an <code>UPDATE</code> statement using a vendor-specific <code>FROM</code> clause. This is supported as well by jOOQ:
</p>
</html><code-pair>
<sql><![CDATA[UPDATE BOOK_ARCHIVE
SET
BOOK_ARCHIVE.TITLE = BOOK.TITLE
FROM BOOK
WHERE BOOK_ARCHIVE.ID = BOOK.ID]]></sql>
<java><![CDATA[create.update(BOOK_ARCHIVE)
.set(BOOK_ARCHIVE.TITLE, BOOK.TITLE)
.from(BOOK)
.where(BOOK_ARCHIVE.ID.eq(BOOK.ID))
.execute();]]></java>
</code-pair><html>
<p>
In many cases, such a joined update statement can be emulated using a correlated subquery, or using updatable views.
</p>
<h3>UPDATE .. RETURNING</h3>
<p>
The Firebird and Postgres databases support a <code>RETURNING</code> clause on their <code>UPDATE</code> statements, similar as the <code>RETURNING</code> clause in <reference id="insert-statement" title="INSERT statements"/>. This is useful to fetch trigger-generated values in one go. An example is given here:

23
jOOQ-manual/src/main/resources/org/jooq/web/manual-3.9.xml
View File

@ -6086,6 +6086,29 @@ create.insertInto(AUTHOR, AUTHOR.FIRST_NAME, AUTHOR.LAST_NAME)
The above row value expressions usages are completely typesafe.
</p>
<h3>UPDATE .. FROM</h3>
<p>
Some databases, including PostgreSQL and SQL Server, support joining additional tables to an <code>UPDATE</code> statement using a vendor-specific <code>FROM</code> clause. This is supported as well by jOOQ:
</p>
</html><code-pair>
<sql><![CDATA[UPDATE BOOK_ARCHIVE
SET
BOOK_ARCHIVE.TITLE = BOOK.TITLE
FROM BOOK
WHERE BOOK_ARCHIVE.ID = BOOK.ID]]></sql>
<java><![CDATA[create.update(BOOK_ARCHIVE)
.set(BOOK_ARCHIVE.TITLE, BOOK.TITLE)
.from(BOOK)
.where(BOOK_ARCHIVE.ID.eq(BOOK.ID))
.execute();]]></java>
</code-pair><html>
<p>
In many cases, such a joined update statement can be emulated using a correlated subquery, or using updatable views.
</p>
<h3>UPDATE .. RETURNING</h3>
<p>
The Firebird and Postgres databases support a <code>RETURNING</code> clause on their <code>UPDATE</code> statements, similar as the <code>RETURNING</code> clause in <reference id="insert-statement" title="INSERT statements"/>. This is useful to fetch trigger-generated values in one go. An example is given here: