[#1053] Redirect from "reference-bnf-notation" section to "sql-parser-grammar", if available

This commit is contained in:
lukaseder 2018-03-23 12:14:41 +01:00
parent 06cc7a7219
commit ea89cfa4ad
13 changed files with 37 additions and 128 deletions

View File

@ -1411,7 +1411,7 @@ create.select()
<h3>jOOQ as an internal domain specific language in Java (a.k.a. the DSL-API)</h3>
<p>
Many other frameworks have similar APIs with similar feature sets. Yet, what makes jOOQ special is its informal <reference id="reference-bnf-notation" title="BNF notation"/> modelling a unified SQL dialect suitable for many vendor-specific dialects, and implementing that BNF notation as a hierarchy of interfaces in Java. This concept is extremely powerful, when <reference id="jooq-in-modern-ides" title="using jOOQ in modern IDEs" /> with syntax completion. Not only can you code much faster, your SQL code will be compile-checked to a certain extent. An example of a DSL query equivalent to the previous one is given here:
Many other frameworks have similar APIs with similar feature sets. Yet, what makes jOOQ special is its informal <a href="https://blog.jooq.org/2012/01/05/the-java-fluent-api-designer-crash-course/">BNF notation</a> modelling a unified SQL dialect suitable for many vendor-specific dialects, and implementing that BNF notation as a hierarchy of interfaces in Java. This concept is extremely powerful, when <reference id="jooq-in-modern-ides" title="using jOOQ in modern IDEs" /> with syntax completion. Not only can you code much faster, your SQL code will be compile-checked to a certain extent. An example of a DSL query equivalent to the previous one is given here:
</p>
</html><java><![CDATA[Factory create = new Factory(connection, dialect);
Result<?> result = create.select()
@ -8962,14 +8962,7 @@ create.selectFrom(AUTHOR)
</sections>
</section>
<section id="reference-bnf-notation">
<title>jOOQ's BNF pseudo-notation</title>
<content><html>
<p>
This chapter will soon contain an overview over jOOQ's API using a pseudo BNF notation.
</p>
</html></content>
</section>
<redirect id="reference-bnf-notation" redirect-to="manual"/>
<section id="reference-credits">
<title>Credits</title>

View File

@ -2015,7 +2015,7 @@ create.select()
<h3>jOOQ as an internal domain specific language in Java (a.k.a. the DSL API)</h3>
<p>
Many other frameworks have similar APIs with similar feature sets. Yet, what makes jOOQ special is its informal <reference id="reference-bnf-notation" title="BNF notation"/> modelling a unified SQL dialect suitable for many vendor-specific dialects, and implementing that BNF notation as a hierarchy of interfaces in Java. This concept is extremely powerful, when <reference id="jooq-in-modern-ides" title="using jOOQ in modern IDEs" /> with syntax completion. Not only can you code much faster, your SQL code will be compile-checked to a certain extent. An example of a DSL query equivalent to the previous one is given here:
Many other frameworks have similar APIs with similar feature sets. Yet, what makes jOOQ special is its informal <a href="https://blog.jooq.org/2012/01/05/the-java-fluent-api-designer-crash-course/">BNF notation</a> modelling a unified SQL dialect suitable for many vendor-specific dialects, and implementing that BNF notation as a hierarchy of interfaces in Java. This concept is extremely powerful, when <reference id="jooq-in-modern-ides" title="using jOOQ in modern IDEs" /> with syntax completion. Not only can you code much faster, your SQL code will be compile-checked to a certain extent. An example of a DSL query equivalent to the previous one is given here:
</p>
</html><java><![CDATA[DSLContext create = DSL.using(connection, dialect);
@ -10431,14 +10431,7 @@ Result<BookRecord> result = create.selectFrom(BOOK).where(BOOK.ID.eq(5)).fetch()
</sections>
</section>
<section id="reference-bnf-notation">
<title>jOOQ's BNF pseudo-notation</title>
<content><html>
<p>
This chapter will soon contain an overview over jOOQ's API using a pseudo BNF notation.
</p>
</html></content>
</section>
<redirect id="reference-bnf-notation" redirect-to="manual"/>
<section id="quality-assurance">
<title>Quality Assurance</title>

View File

@ -1517,7 +1517,7 @@ object Test { //
With this philosophy in mind, SQL building is the main feature of jOOQ. All other features (such as <reference id="sql-execution" title="SQL execution"/> and <reference id="code-generation" title="code generation"/>) are mere convenience built on top of jOOQ's SQL building capabilities.
</p>
<p>
This section explains all about the various syntax elements involved with jOOQ's SQL building capabilities. For a complete overview of all syntax elements, please refer to the manual's sections about <reference id="dsl-mapping-rules" title="SQL to DSL mapping rules"/> as well as <reference id="reference-bnf-notation" title="jOOQ's BNF notation"/>
This section explains all about the various syntax elements involved with jOOQ's SQL building capabilities. For a complete overview of all syntax elements, please refer to the manual's sections about <reference id="dsl-mapping-rules" title="SQL to DSL mapping rules"/>.
</p>
</html></content>
@ -2393,7 +2393,7 @@ create.select()
<h3>jOOQ as an internal domain specific language in Java (a.k.a. the DSL API)</h3>
<p>
Many other frameworks have similar APIs with similar feature sets. Yet, what makes jOOQ special is its informal <reference id="reference-bnf-notation" title="BNF notation"/> modelling a unified SQL dialect suitable for many vendor-specific dialects, and implementing that BNF notation as a hierarchy of interfaces in Java. This concept is extremely powerful, when <reference id="jooq-in-modern-ides" title="using jOOQ in modern IDEs" /> with syntax completion. Not only can you code much faster, your SQL code will be compile-checked to a certain extent. An example of a DSL query equivalent to the previous one is given here:
Many other frameworks have similar APIs with similar feature sets. Yet, what makes jOOQ special is its informal <a href="https://blog.jooq.org/2012/01/05/the-java-fluent-api-designer-crash-course/">BNF notation</a> modelling a unified SQL dialect suitable for many vendor-specific dialects, and implementing that BNF notation as a hierarchy of interfaces in Java. This concept is extremely powerful, when <reference id="jooq-in-modern-ides" title="using jOOQ in modern IDEs" /> with syntax completion. Not only can you code much faster, your SQL code will be compile-checked to a certain extent. An example of a DSL query equivalent to the previous one is given here:
</p>
</html><java><![CDATA[DSLContext create = DSL.using(connection, dialect);
@ -11240,14 +11240,7 @@ FROM t</sql><html>
</html></content>
</section>
<section id="reference-bnf-notation">
<title>jOOQ's BNF pseudo-notation</title>
<content><html>
<p>
This chapter will soon contain an overview over jOOQ's API using a pseudo BNF notation.
</p>
</html></content>
</section>
<redirect id="reference-bnf-notation" redirect-to="manual"/>
<section id="quality-assurance">
<title>Quality Assurance</title>

View File

@ -2891,7 +2891,7 @@ fun main(args: Array<String>) {
With this philosophy in mind, SQL building is the main feature of jOOQ. All other features (such as <reference id="sql-execution" title="SQL execution"/> and <reference id="code-generation" title="code generation"/>) are mere convenience built on top of jOOQ's SQL building capabilities.
</p>
<p>
This section explains all about the various syntax elements involved with jOOQ's SQL building capabilities. For a complete overview of all syntax elements, please refer to the manual's sections about <reference id="dsl-mapping-rules" title="SQL to DSL mapping rules"/> as well as <reference id="reference-bnf-notation" title="jOOQ's BNF notation"/>
This section explains all about the various syntax elements involved with jOOQ's SQL building capabilities. For a complete overview of all syntax elements, please refer to the manual's sections about <reference id="dsl-mapping-rules" title="SQL to DSL mapping rules"/>.
</p>
</html></content>
@ -4171,7 +4171,7 @@ create.select()
<h3>jOOQ as an internal domain specific language in Java (a.k.a. the DSL API)</h3>
<p>
Many other frameworks have similar APIs with similar feature sets. Yet, what makes jOOQ special is its informal <reference id="reference-bnf-notation" title="BNF notation"/> modelling a unified SQL dialect suitable for many vendor-specific dialects, and implementing that BNF notation as a hierarchy of interfaces in Java. This concept is extremely powerful, when <reference id="jooq-in-modern-ides" title="using jOOQ in modern IDEs" /> with syntax completion. Not only can you code much faster, your SQL code will be compile-checked to a certain extent. An example of a DSL query equivalent to the previous one is given here:
Many other frameworks have similar APIs with similar feature sets. Yet, what makes jOOQ special is its informal <a href="https://blog.jooq.org/2012/01/05/the-java-fluent-api-designer-crash-course/">BNF notation</a> modelling a unified SQL dialect suitable for many vendor-specific dialects, and implementing that BNF notation as a hierarchy of interfaces in Java. This concept is extremely powerful, when <reference id="jooq-in-modern-ides" title="using jOOQ in modern IDEs" /> with syntax completion. Not only can you code much faster, your SQL code will be compile-checked to a certain extent. An example of a DSL query equivalent to the previous one is given here:
</p>
</html><java><![CDATA[DSLContext create = DSL.using(connection, dialect);
@ -19229,14 +19229,7 @@ FROM t</sql><html>
</html></content>
</section>
<section id="reference-bnf-notation">
<title>jOOQ's BNF pseudo-notation</title>
<content><html>
<p>
This chapter will soon contain an overview over jOOQ's API using a pseudo BNF notation.
</p>
</html></content>
</section>
<redirect id="reference-bnf-notation" redirect-to="sql-parser-grammar"/>
<section id="quality-assurance">
<title>Quality Assurance</title>

View File

@ -2891,7 +2891,7 @@ fun main(args: Array<String>) {
With this philosophy in mind, SQL building is the main feature of jOOQ. All other features (such as <reference id="sql-execution" title="SQL execution"/> and <reference id="code-generation" title="code generation"/>) are mere convenience built on top of jOOQ's SQL building capabilities.
</p>
<p>
This section explains all about the various syntax elements involved with jOOQ's SQL building capabilities. For a complete overview of all syntax elements, please refer to the manual's sections about <reference id="dsl-mapping-rules" title="SQL to DSL mapping rules"/> as well as <reference id="reference-bnf-notation" title="jOOQ's BNF notation"/>
This section explains all about the various syntax elements involved with jOOQ's SQL building capabilities. For a complete overview of all syntax elements, please refer to the manual's sections about <reference id="dsl-mapping-rules" title="SQL to DSL mapping rules"/>.
</p>
</html></content>
@ -4171,7 +4171,7 @@ create.select()
<h3>jOOQ as an internal domain specific language in Java (a.k.a. the DSL API)</h3>
<p>
Many other frameworks have similar APIs with similar feature sets. Yet, what makes jOOQ special is its informal <reference id="reference-bnf-notation" title="BNF notation"/> modelling a unified SQL dialect suitable for many vendor-specific dialects, and implementing that BNF notation as a hierarchy of interfaces in Java. This concept is extremely powerful, when <reference id="jooq-in-modern-ides" title="using jOOQ in modern IDEs" /> with syntax completion. Not only can you code much faster, your SQL code will be compile-checked to a certain extent. An example of a DSL query equivalent to the previous one is given here:
Many other frameworks have similar APIs with similar feature sets. Yet, what makes jOOQ special is its informal <a href="https://blog.jooq.org/2012/01/05/the-java-fluent-api-designer-crash-course/">BNF notation</a> modelling a unified SQL dialect suitable for many vendor-specific dialects, and implementing that BNF notation as a hierarchy of interfaces in Java. This concept is extremely powerful, when <reference id="jooq-in-modern-ides" title="using jOOQ in modern IDEs" /> with syntax completion. Not only can you code much faster, your SQL code will be compile-checked to a certain extent. An example of a DSL query equivalent to the previous one is given here:
</p>
</html><java><![CDATA[DSLContext create = DSL.using(connection, dialect);
@ -19464,14 +19464,7 @@ FROM t</sql><html>
</html></content>
</section>
<section id="reference-bnf-notation">
<title>jOOQ's BNF pseudo-notation</title>
<content><html>
<p>
This chapter will soon contain an overview over jOOQ's API using a pseudo BNF notation.
</p>
</html></content>
</section>
<redirect id="reference-bnf-notation" redirect-to="sql-parser-grammar"/>
<section id="quality-assurance">
<title>Quality Assurance</title>

View File

@ -1573,7 +1573,7 @@ object Test { //
With this philosophy in mind, SQL building is the main feature of jOOQ. All other features (such as <reference id="sql-execution" title="SQL execution"/> and <reference id="code-generation" title="code generation"/>) are mere convenience built on top of jOOQ's SQL building capabilities.
</p>
<p>
This section explains all about the various syntax elements involved with jOOQ's SQL building capabilities. For a complete overview of all syntax elements, please refer to the manual's sections about <reference id="dsl-mapping-rules" title="SQL to DSL mapping rules"/> as well as <reference id="reference-bnf-notation" title="jOOQ's BNF notation"/>
This section explains all about the various syntax elements involved with jOOQ's SQL building capabilities. For a complete overview of all syntax elements, please refer to the manual's sections about <reference id="dsl-mapping-rules" title="SQL to DSL mapping rules"/>.
</p>
</html></content>
@ -2497,7 +2497,7 @@ create.select()
<h3>jOOQ as an internal domain specific language in Java (a.k.a. the DSL API)</h3>
<p>
Many other frameworks have similar APIs with similar feature sets. Yet, what makes jOOQ special is its informal <reference id="reference-bnf-notation" title="BNF notation"/> modelling a unified SQL dialect suitable for many vendor-specific dialects, and implementing that BNF notation as a hierarchy of interfaces in Java. This concept is extremely powerful, when <reference id="jooq-in-modern-ides" title="using jOOQ in modern IDEs" /> with syntax completion. Not only can you code much faster, your SQL code will be compile-checked to a certain extent. An example of a DSL query equivalent to the previous one is given here:
Many other frameworks have similar APIs with similar feature sets. Yet, what makes jOOQ special is its informal <a href="https://blog.jooq.org/2012/01/05/the-java-fluent-api-designer-crash-course/">BNF notation</a> modelling a unified SQL dialect suitable for many vendor-specific dialects, and implementing that BNF notation as a hierarchy of interfaces in Java. This concept is extremely powerful, when <reference id="jooq-in-modern-ides" title="using jOOQ in modern IDEs" /> with syntax completion. Not only can you code much faster, your SQL code will be compile-checked to a certain extent. An example of a DSL query equivalent to the previous one is given here:
</p>
</html><java><![CDATA[DSLContext create = DSL.using(connection, dialect);
@ -12061,14 +12061,7 @@ FROM t</sql><html>
</html></content>
</section>
<section id="reference-bnf-notation">
<title>jOOQ's BNF pseudo-notation</title>
<content><html>
<p>
This chapter will soon contain an overview over jOOQ's API using a pseudo BNF notation.
</p>
</html></content>
</section>
<redirect id="reference-bnf-notation" redirect-to="manual"/>
<section id="quality-assurance">
<title>Quality Assurance</title>

View File

@ -2033,7 +2033,7 @@ DSL.using(sql.connection)
With this philosophy in mind, SQL building is the main feature of jOOQ. All other features (such as <reference id="sql-execution" title="SQL execution"/> and <reference id="code-generation" title="code generation"/>) are mere convenience built on top of jOOQ's SQL building capabilities.
</p>
<p>
This section explains all about the various syntax elements involved with jOOQ's SQL building capabilities. For a complete overview of all syntax elements, please refer to the manual's sections about <reference id="dsl-mapping-rules" title="SQL to DSL mapping rules"/> as well as <reference id="reference-bnf-notation" title="jOOQ's BNF notation"/>
This section explains all about the various syntax elements involved with jOOQ's SQL building capabilities. For a complete overview of all syntax elements, please refer to the manual's sections about <reference id="dsl-mapping-rules" title="SQL to DSL mapping rules"/>.
</p>
</html></content>
@ -2981,7 +2981,7 @@ create.select()
<h3>jOOQ as an internal domain specific language in Java (a.k.a. the DSL API)</h3>
<p>
Many other frameworks have similar APIs with similar feature sets. Yet, what makes jOOQ special is its informal <reference id="reference-bnf-notation" title="BNF notation"/> modelling a unified SQL dialect suitable for many vendor-specific dialects, and implementing that BNF notation as a hierarchy of interfaces in Java. This concept is extremely powerful, when <reference id="jooq-in-modern-ides" title="using jOOQ in modern IDEs" /> with syntax completion. Not only can you code much faster, your SQL code will be compile-checked to a certain extent. An example of a DSL query equivalent to the previous one is given here:
Many other frameworks have similar APIs with similar feature sets. Yet, what makes jOOQ special is its informal <a href="https://blog.jooq.org/2012/01/05/the-java-fluent-api-designer-crash-course/">BNF notation</a> modelling a unified SQL dialect suitable for many vendor-specific dialects, and implementing that BNF notation as a hierarchy of interfaces in Java. This concept is extremely powerful, when <reference id="jooq-in-modern-ides" title="using jOOQ in modern IDEs" /> with syntax completion. Not only can you code much faster, your SQL code will be compile-checked to a certain extent. An example of a DSL query equivalent to the previous one is given here:
</p>
</html><java><![CDATA[DSLContext create = DSL.using(connection, dialect);
@ -12994,14 +12994,7 @@ FROM t</sql><html>
</html></content>
</section>
<section id="reference-bnf-notation">
<title>jOOQ's BNF pseudo-notation</title>
<content><html>
<p>
This chapter will soon contain an overview over jOOQ's API using a pseudo BNF notation.
</p>
</html></content>
</section>
<redirect id="reference-bnf-notation" redirect-to="manual"/>
<section id="quality-assurance">
<title>Quality Assurance</title>

View File

@ -2531,7 +2531,7 @@ DSL.using(sql.connection)
With this philosophy in mind, SQL building is the main feature of jOOQ. All other features (such as <reference id="sql-execution" title="SQL execution"/> and <reference id="code-generation" title="code generation"/>) are mere convenience built on top of jOOQ's SQL building capabilities.
</p>
<p>
This section explains all about the various syntax elements involved with jOOQ's SQL building capabilities. For a complete overview of all syntax elements, please refer to the manual's sections about <reference id="dsl-mapping-rules" title="SQL to DSL mapping rules"/> as well as <reference id="reference-bnf-notation" title="jOOQ's BNF notation"/>
This section explains all about the various syntax elements involved with jOOQ's SQL building capabilities. For a complete overview of all syntax elements, please refer to the manual's sections about <reference id="dsl-mapping-rules" title="SQL to DSL mapping rules"/>.
</p>
</html></content>
@ -3592,7 +3592,7 @@ create.select()
<h3>jOOQ as an internal domain specific language in Java (a.k.a. the DSL API)</h3>
<p>
Many other frameworks have similar APIs with similar feature sets. Yet, what makes jOOQ special is its informal <reference id="reference-bnf-notation" title="BNF notation"/> modelling a unified SQL dialect suitable for many vendor-specific dialects, and implementing that BNF notation as a hierarchy of interfaces in Java. This concept is extremely powerful, when <reference id="jooq-in-modern-ides" title="using jOOQ in modern IDEs" /> with syntax completion. Not only can you code much faster, your SQL code will be compile-checked to a certain extent. An example of a DSL query equivalent to the previous one is given here:
Many other frameworks have similar APIs with similar feature sets. Yet, what makes jOOQ special is its informal <a href="https://blog.jooq.org/2012/01/05/the-java-fluent-api-designer-crash-course/">BNF notation</a> modelling a unified SQL dialect suitable for many vendor-specific dialects, and implementing that BNF notation as a hierarchy of interfaces in Java. This concept is extremely powerful, when <reference id="jooq-in-modern-ides" title="using jOOQ in modern IDEs" /> with syntax completion. Not only can you code much faster, your SQL code will be compile-checked to a certain extent. An example of a DSL query equivalent to the previous one is given here:
</p>
</html><java><![CDATA[DSLContext create = DSL.using(connection, dialect);
@ -14373,14 +14373,7 @@ FROM t</sql><html>
</html></content>
</section>
<section id="reference-bnf-notation">
<title>jOOQ's BNF pseudo-notation</title>
<content><html>
<p>
This chapter will soon contain an overview over jOOQ's API using a pseudo BNF notation.
</p>
</html></content>
</section>
<redirect id="reference-bnf-notation" redirect-to="manual"/>
<section id="quality-assurance">
<title>Quality Assurance</title>

View File

@ -2731,7 +2731,7 @@ DSL.using(sql.connection)
With this philosophy in mind, SQL building is the main feature of jOOQ. All other features (such as <reference id="sql-execution" title="SQL execution"/> and <reference id="code-generation" title="code generation"/>) are mere convenience built on top of jOOQ's SQL building capabilities.
</p>
<p>
This section explains all about the various syntax elements involved with jOOQ's SQL building capabilities. For a complete overview of all syntax elements, please refer to the manual's sections about <reference id="dsl-mapping-rules" title="SQL to DSL mapping rules"/> as well as <reference id="reference-bnf-notation" title="jOOQ's BNF notation"/>
This section explains all about the various syntax elements involved with jOOQ's SQL building capabilities. For a complete overview of all syntax elements, please refer to the manual's sections about <reference id="dsl-mapping-rules" title="SQL to DSL mapping rules"/>.
</p>
</html></content>
@ -3792,7 +3792,7 @@ create.select()
<h3>jOOQ as an internal domain specific language in Java (a.k.a. the DSL API)</h3>
<p>
Many other frameworks have similar APIs with similar feature sets. Yet, what makes jOOQ special is its informal <reference id="reference-bnf-notation" title="BNF notation"/> modelling a unified SQL dialect suitable for many vendor-specific dialects, and implementing that BNF notation as a hierarchy of interfaces in Java. This concept is extremely powerful, when <reference id="jooq-in-modern-ides" title="using jOOQ in modern IDEs" /> with syntax completion. Not only can you code much faster, your SQL code will be compile-checked to a certain extent. An example of a DSL query equivalent to the previous one is given here:
Many other frameworks have similar APIs with similar feature sets. Yet, what makes jOOQ special is its informal <a href="https://blog.jooq.org/2012/01/05/the-java-fluent-api-designer-crash-course/">BNF notation</a> modelling a unified SQL dialect suitable for many vendor-specific dialects, and implementing that BNF notation as a hierarchy of interfaces in Java. This concept is extremely powerful, when <reference id="jooq-in-modern-ides" title="using jOOQ in modern IDEs" /> with syntax completion. Not only can you code much faster, your SQL code will be compile-checked to a certain extent. An example of a DSL query equivalent to the previous one is given here:
</p>
</html><java><![CDATA[DSLContext create = DSL.using(connection, dialect);
@ -15139,14 +15139,7 @@ FROM t</sql><html>
</html></content>
</section>
<section id="reference-bnf-notation">
<title>jOOQ's BNF pseudo-notation</title>
<content><html>
<p>
This chapter will soon contain an overview over jOOQ's API using a pseudo BNF notation.
</p>
</html></content>
</section>
<redirect id="reference-bnf-notation" redirect-to="manual"/>
<section id="quality-assurance">
<title>Quality Assurance</title>

View File

@ -2735,7 +2735,7 @@ DSL.using(sql.connection)
With this philosophy in mind, SQL building is the main feature of jOOQ. All other features (such as <reference id="sql-execution" title="SQL execution"/> and <reference id="code-generation" title="code generation"/>) are mere convenience built on top of jOOQ's SQL building capabilities.
</p>
<p>
This section explains all about the various syntax elements involved with jOOQ's SQL building capabilities. For a complete overview of all syntax elements, please refer to the manual's sections about <reference id="dsl-mapping-rules" title="SQL to DSL mapping rules"/> as well as <reference id="reference-bnf-notation" title="jOOQ's BNF notation"/>
This section explains all about the various syntax elements involved with jOOQ's SQL building capabilities. For a complete overview of all syntax elements, please refer to the manual's sections about <reference id="dsl-mapping-rules" title="SQL to DSL mapping rules"/>.
</p>
</html></content>
@ -3797,7 +3797,7 @@ create.select()
<h3>jOOQ as an internal domain specific language in Java (a.k.a. the DSL API)</h3>
<p>
Many other frameworks have similar APIs with similar feature sets. Yet, what makes jOOQ special is its informal <reference id="reference-bnf-notation" title="BNF notation"/> modelling a unified SQL dialect suitable for many vendor-specific dialects, and implementing that BNF notation as a hierarchy of interfaces in Java. This concept is extremely powerful, when <reference id="jooq-in-modern-ides" title="using jOOQ in modern IDEs" /> with syntax completion. Not only can you code much faster, your SQL code will be compile-checked to a certain extent. An example of a DSL query equivalent to the previous one is given here:
Many other frameworks have similar APIs with similar feature sets. Yet, what makes jOOQ special is its informal <a href="https://blog.jooq.org/2012/01/05/the-java-fluent-api-designer-crash-course/">BNF notation</a> modelling a unified SQL dialect suitable for many vendor-specific dialects, and implementing that BNF notation as a hierarchy of interfaces in Java. This concept is extremely powerful, when <reference id="jooq-in-modern-ides" title="using jOOQ in modern IDEs" /> with syntax completion. Not only can you code much faster, your SQL code will be compile-checked to a certain extent. An example of a DSL query equivalent to the previous one is given here:
</p>
</html><java><![CDATA[DSLContext create = DSL.using(connection, dialect);
@ -16175,14 +16175,7 @@ FROM t</sql><html>
</html></content>
</section>
<section id="reference-bnf-notation">
<title>jOOQ's BNF pseudo-notation</title>
<content><html>
<p>
This chapter will soon contain an overview over jOOQ's API using a pseudo BNF notation.
</p>
</html></content>
</section>
<redirect id="reference-bnf-notation" redirect-to="manual"/>
<section id="quality-assurance">
<title>Quality Assurance</title>

View File

@ -2878,7 +2878,7 @@ fun main(args: Array<String>) {
With this philosophy in mind, SQL building is the main feature of jOOQ. All other features (such as <reference id="sql-execution" title="SQL execution"/> and <reference id="code-generation" title="code generation"/>) are mere convenience built on top of jOOQ's SQL building capabilities.
</p>
<p>
This section explains all about the various syntax elements involved with jOOQ's SQL building capabilities. For a complete overview of all syntax elements, please refer to the manual's sections about <reference id="dsl-mapping-rules" title="SQL to DSL mapping rules"/> as well as <reference id="reference-bnf-notation" title="jOOQ's BNF notation"/>
This section explains all about the various syntax elements involved with jOOQ's SQL building capabilities. For a complete overview of all syntax elements, please refer to the manual's sections about <reference id="dsl-mapping-rules" title="SQL to DSL mapping rules"/>.
</p>
</html></content>
@ -3964,7 +3964,7 @@ create.select()
<h3>jOOQ as an internal domain specific language in Java (a.k.a. the DSL API)</h3>
<p>
Many other frameworks have similar APIs with similar feature sets. Yet, what makes jOOQ special is its informal <reference id="reference-bnf-notation" title="BNF notation"/> modelling a unified SQL dialect suitable for many vendor-specific dialects, and implementing that BNF notation as a hierarchy of interfaces in Java. This concept is extremely powerful, when <reference id="jooq-in-modern-ides" title="using jOOQ in modern IDEs" /> with syntax completion. Not only can you code much faster, your SQL code will be compile-checked to a certain extent. An example of a DSL query equivalent to the previous one is given here:
Many other frameworks have similar APIs with similar feature sets. Yet, what makes jOOQ special is its informal <a href="https://blog.jooq.org/2012/01/05/the-java-fluent-api-designer-crash-course/">BNF notation</a> modelling a unified SQL dialect suitable for many vendor-specific dialects, and implementing that BNF notation as a hierarchy of interfaces in Java. This concept is extremely powerful, when <reference id="jooq-in-modern-ides" title="using jOOQ in modern IDEs" /> with syntax completion. Not only can you code much faster, your SQL code will be compile-checked to a certain extent. An example of a DSL query equivalent to the previous one is given here:
</p>
</html><java><![CDATA[DSLContext create = DSL.using(connection, dialect);
@ -16617,14 +16617,7 @@ FROM t</sql><html>
</html></content>
</section>
<section id="reference-bnf-notation">
<title>jOOQ's BNF pseudo-notation</title>
<content><html>
<p>
This chapter will soon contain an overview over jOOQ's API using a pseudo BNF notation.
</p>
</html></content>
</section>
<redirect id="reference-bnf-notation" redirect-to="manual"/>
<section id="quality-assurance">
<title>Quality Assurance</title>

View File

@ -2892,7 +2892,7 @@ fun main(args: Array<String>) {
With this philosophy in mind, SQL building is the main feature of jOOQ. All other features (such as <reference id="sql-execution" title="SQL execution"/> and <reference id="code-generation" title="code generation"/>) are mere convenience built on top of jOOQ's SQL building capabilities.
</p>
<p>
This section explains all about the various syntax elements involved with jOOQ's SQL building capabilities. For a complete overview of all syntax elements, please refer to the manual's sections about <reference id="dsl-mapping-rules" title="SQL to DSL mapping rules"/> as well as <reference id="reference-bnf-notation" title="jOOQ's BNF notation"/>
This section explains all about the various syntax elements involved with jOOQ's SQL building capabilities. For a complete overview of all syntax elements, please refer to the manual's sections about <reference id="dsl-mapping-rules" title="SQL to DSL mapping rules"/>.
</p>
</html></content>
@ -4090,7 +4090,7 @@ create.select()
<h3>jOOQ as an internal domain specific language in Java (a.k.a. the DSL API)</h3>
<p>
Many other frameworks have similar APIs with similar feature sets. Yet, what makes jOOQ special is its informal <reference id="reference-bnf-notation" title="BNF notation"/> modelling a unified SQL dialect suitable for many vendor-specific dialects, and implementing that BNF notation as a hierarchy of interfaces in Java. This concept is extremely powerful, when <reference id="jooq-in-modern-ides" title="using jOOQ in modern IDEs" /> with syntax completion. Not only can you code much faster, your SQL code will be compile-checked to a certain extent. An example of a DSL query equivalent to the previous one is given here:
Many other frameworks have similar APIs with similar feature sets. Yet, what makes jOOQ special is its informal <a href="https://blog.jooq.org/2012/01/05/the-java-fluent-api-designer-crash-course/">BNF notation</a> modelling a unified SQL dialect suitable for many vendor-specific dialects, and implementing that BNF notation as a hierarchy of interfaces in Java. This concept is extremely powerful, when <reference id="jooq-in-modern-ides" title="using jOOQ in modern IDEs" /> with syntax completion. Not only can you code much faster, your SQL code will be compile-checked to a certain extent. An example of a DSL query equivalent to the previous one is given here:
</p>
</html><java><![CDATA[DSLContext create = DSL.using(connection, dialect);
@ -16911,14 +16911,7 @@ FROM t</sql><html>
</html></content>
</section>
<section id="reference-bnf-notation">
<title>jOOQ's BNF pseudo-notation</title>
<content><html>
<p>
This chapter will soon contain an overview over jOOQ's API using a pseudo BNF notation.
</p>
</html></content>
</section>
<redirect id="reference-bnf-notation" redirect-to="manual"/>
<section id="quality-assurance">
<title>Quality Assurance</title>

View File

@ -2891,7 +2891,7 @@ fun main(args: Array<String>) {
With this philosophy in mind, SQL building is the main feature of jOOQ. All other features (such as <reference id="sql-execution" title="SQL execution"/> and <reference id="code-generation" title="code generation"/>) are mere convenience built on top of jOOQ's SQL building capabilities.
</p>
<p>
This section explains all about the various syntax elements involved with jOOQ's SQL building capabilities. For a complete overview of all syntax elements, please refer to the manual's sections about <reference id="dsl-mapping-rules" title="SQL to DSL mapping rules"/> as well as <reference id="reference-bnf-notation" title="jOOQ's BNF notation"/>
This section explains all about the various syntax elements involved with jOOQ's SQL building capabilities. For a complete overview of all syntax elements, please refer to the manual's sections about <reference id="dsl-mapping-rules" title="SQL to DSL mapping rules"/>.
</p>
</html></content>
@ -4171,7 +4171,7 @@ create.select()
<h3>jOOQ as an internal domain specific language in Java (a.k.a. the DSL API)</h3>
<p>
Many other frameworks have similar APIs with similar feature sets. Yet, what makes jOOQ special is its informal <reference id="reference-bnf-notation" title="BNF notation"/> modelling a unified SQL dialect suitable for many vendor-specific dialects, and implementing that BNF notation as a hierarchy of interfaces in Java. This concept is extremely powerful, when <reference id="jooq-in-modern-ides" title="using jOOQ in modern IDEs" /> with syntax completion. Not only can you code much faster, your SQL code will be compile-checked to a certain extent. An example of a DSL query equivalent to the previous one is given here:
Many other frameworks have similar APIs with similar feature sets. Yet, what makes jOOQ special is its informal <a href="https://blog.jooq.org/2012/01/05/the-java-fluent-api-designer-crash-course/">BNF notation</a> modelling a unified SQL dialect suitable for many vendor-specific dialects, and implementing that BNF notation as a hierarchy of interfaces in Java. This concept is extremely powerful, when <reference id="jooq-in-modern-ides" title="using jOOQ in modern IDEs" /> with syntax completion. Not only can you code much faster, your SQL code will be compile-checked to a certain extent. An example of a DSL query equivalent to the previous one is given here:
</p>
</html><java><![CDATA[DSLContext create = DSL.using(connection, dialect);
@ -18807,14 +18807,7 @@ FROM t</sql><html>
</html></content>
</section>
<section id="reference-bnf-notation">
<title>jOOQ's BNF pseudo-notation</title>
<content><html>
<p>
This chapter will soon contain an overview over jOOQ's API using a pseudo BNF notation.
</p>
</html></content>
</section>
<redirect id="reference-bnf-notation" redirect-to="manual"/>
<section id="quality-assurance">
<title>Quality Assurance</title>