[#7453] Update docs: SQL Azure is now called Azure SQL Database

This commit is contained in:
lukaseder 2018-05-02 17:05:10 +02:00
parent eb5f95f307
commit 7a8dcbb4c7
13 changed files with 13 additions and 13 deletions

View File

@ -8777,11 +8777,11 @@ create.selectFrom(AUTHOR)
Any of the following databases might be available in the future
</p>
<ul>
<li>Azure SQL Database</li>
<li>Informix</li>
<li>Interbase</li>
<li>MS Access</li>
<li>MS Excel</li>
<li>SQL Azure</li>
<li>Sybase SQL Anywhere OnDemand</li>
<li>Teradata</li>
</ul>

View File

@ -10251,6 +10251,7 @@ Result<BookRecord> result = create.selectFrom(BOOK).where(BOOK.ID.eq(5)).fetch()
Every RDMBS out there has its own little specialties. jOOQ considers those specialties as much as possible, while trying to standardise the behaviour in jOOQ. In order to increase the quality of jOOQ, some 70 unit tests are run for syntax and variable binding verification, as well as some 400 integration tests with an overall of around 4000 queries for any of these databases:
</p>
<ul>
<li>Azure SQL Database</li>
<li>CUBRID</li>
<li>DB2</li>
<li>Derby</li>
@ -10263,7 +10264,6 @@ Result<BookRecord> result = create.selectFrom(BOOK).where(BOOK.ID.eq(5)).fetch()
<li>Oracle</li>
<li>PostgreSQL</li>
<li>SQLite</li>
<li>SQL Azure</li>
<li>SQL Server</li>
<li>Sybase Adaptive Server Enterprise</li>
<li>Sybase SQL Anywhere</li>

View File

@ -10875,6 +10875,7 @@ Result<BookRecord> result = create.selectFrom(BOOK).where(BOOK.ID.eq(5)).fetch()
Every RDMBS out there has its own little specialties. jOOQ considers those specialties as much as possible, while trying to standardise the behaviour in jOOQ. In order to increase the quality of jOOQ, some 70 unit tests are run for syntax and variable binding verification, as well as some 400 integration tests with an overall of around 4000 queries for any of these databases:
</p>
<ul>
<li>Azure SQL Database</li>
<li>CUBRID</li>
<li>DB2</li>
<li>Derby</li>
@ -10887,7 +10888,6 @@ Result<BookRecord> result = create.selectFrom(BOOK).where(BOOK.ID.eq(5)).fetch()
<li>Oracle</li>
<li>PostgreSQL</li>
<li>SQLite</li>
<li>SQL Azure</li>
<li>SQL Server</li>
<li>Sybase Adaptive Server Enterprise</li>
<li>Sybase SQL Anywhere</li>

View File

@ -19012,6 +19012,7 @@ Result<Record2<String, String>> result = create.select( Actor.ACTOR.FIRST_NAME,
Every RDMBS out there has its own little specialties. jOOQ considers those specialties as much as possible, while trying to standardise the behaviour in jOOQ. In order to increase the quality of jOOQ, some 70 unit tests are run for syntax and variable binding verification, as well as some 400 integration tests with an overall of around 4000 queries for any of these databases:
</p>
<ul>
<li>Azure SQL Database</li>
<li>CUBRID</li>
<li>DB2</li>
<li>Derby</li>
@ -19027,7 +19028,6 @@ Result<Record2<String, String>> result = create.select( Actor.ACTOR.FIRST_NAME,
<li>Oracle</li>
<li>PostgreSQL</li>
<li>SQLite</li>
<li>SQL Azure</li>
<li>SQL Server</li>
<li>Sybase Adaptive Server Enterprise</li>
<li>Sybase SQL Anywhere</li>

View File

@ -19695,6 +19695,7 @@ Result<Record2<String, String>> result = create.select( Actor.ACTOR.FIRST_NAME,
Every RDMBS out there has its own little specialties. jOOQ considers those specialties as much as possible, while trying to standardise the behaviour in jOOQ. In order to increase the quality of jOOQ, some 70 unit tests are run for syntax and variable binding verification, as well as some 400 integration tests with an overall of around 4000 queries for any of these databases:
</p>
<ul>
<li>Azure SQL Database</li>
<li>CUBRID</li>
<li>DB2</li>
<li>Derby</li>
@ -19710,7 +19711,6 @@ Result<Record2<String, String>> result = create.select( Actor.ACTOR.FIRST_NAME,
<li>Oracle</li>
<li>PostgreSQL</li>
<li>SQLite</li>
<li>SQL Azure</li>
<li>SQL Server</li>
<li>Sybase Adaptive Server Enterprise</li>
<li>Sybase SQL Anywhere</li>

View File

@ -11685,6 +11685,7 @@ Result<BookRecord> result = create.selectFrom(BOOK).where(BOOK.ID.eq(5)).fetch()
Every RDMBS out there has its own little specialties. jOOQ considers those specialties as much as possible, while trying to standardise the behaviour in jOOQ. In order to increase the quality of jOOQ, some 70 unit tests are run for syntax and variable binding verification, as well as some 400 integration tests with an overall of around 4000 queries for any of these databases:
</p>
<ul>
<li>Azure SQL Database</li>
<li>CUBRID</li>
<li>DB2</li>
<li>Derby</li>
@ -11697,7 +11698,6 @@ Result<BookRecord> result = create.selectFrom(BOOK).where(BOOK.ID.eq(5)).fetch()
<li>Oracle</li>
<li>PostgreSQL</li>
<li>SQLite</li>
<li>SQL Azure</li>
<li>SQL Server</li>
<li>Sybase Adaptive Server Enterprise</li>
<li>Sybase SQL Anywhere</li>

View File

@ -12617,6 +12617,7 @@ Result<Record2<String, String>> result = create.select( Actor.ACTOR.FIRST_NAME,
Every RDMBS out there has its own little specialties. jOOQ considers those specialties as much as possible, while trying to standardise the behaviour in jOOQ. In order to increase the quality of jOOQ, some 70 unit tests are run for syntax and variable binding verification, as well as some 400 integration tests with an overall of around 4000 queries for any of these databases:
</p>
<ul>
<li>Azure SQL Database</li>
<li>CUBRID</li>
<li>DB2</li>
<li>Derby</li>
@ -12630,7 +12631,6 @@ Result<Record2<String, String>> result = create.select( Actor.ACTOR.FIRST_NAME,
<li>Oracle</li>
<li>PostgreSQL</li>
<li>SQLite</li>
<li>SQL Azure</li>
<li>SQL Server</li>
<li>Sybase Adaptive Server Enterprise</li>
<li>Sybase SQL Anywhere</li>

View File

@ -13996,6 +13996,7 @@ Result<Record2<String, String>> result = create.select( Actor.ACTOR.FIRST_NAME,
Every RDMBS out there has its own little specialties. jOOQ considers those specialties as much as possible, while trying to standardise the behaviour in jOOQ. In order to increase the quality of jOOQ, some 70 unit tests are run for syntax and variable binding verification, as well as some 400 integration tests with an overall of around 4000 queries for any of these databases:
</p>
<ul>
<li>Azure SQL Database</li>
<li>CUBRID</li>
<li>DB2</li>
<li>Derby</li>
@ -14009,7 +14010,6 @@ Result<Record2<String, String>> result = create.select( Actor.ACTOR.FIRST_NAME,
<li>Oracle</li>
<li>PostgreSQL</li>
<li>SQLite</li>
<li>SQL Azure</li>
<li>SQL Server</li>
<li>Sybase Adaptive Server Enterprise</li>
<li>Sybase SQL Anywhere</li>

View File

@ -14703,6 +14703,7 @@ Result<Record2<String, String>> result = create.select( Actor.ACTOR.FIRST_NAME,
Every RDMBS out there has its own little specialties. jOOQ considers those specialties as much as possible, while trying to standardise the behaviour in jOOQ. In order to increase the quality of jOOQ, some 70 unit tests are run for syntax and variable binding verification, as well as some 400 integration tests with an overall of around 4000 queries for any of these databases:
</p>
<ul>
<li>Azure SQL Database</li>
<li>CUBRID</li>
<li>DB2</li>
<li>Derby</li>
@ -14717,7 +14718,6 @@ Result<Record2<String, String>> result = create.select( Actor.ACTOR.FIRST_NAME,
<li>Oracle</li>
<li>PostgreSQL</li>
<li>SQLite</li>
<li>SQL Azure</li>
<li>SQL Server</li>
<li>Sybase Adaptive Server Enterprise</li>
<li>Sybase SQL Anywhere</li>

View File

@ -15738,6 +15738,7 @@ Result<Record2<String, String>> result = create.select( Actor.ACTOR.FIRST_NAME,
Every RDMBS out there has its own little specialties. jOOQ considers those specialties as much as possible, while trying to standardise the behaviour in jOOQ. In order to increase the quality of jOOQ, some 70 unit tests are run for syntax and variable binding verification, as well as some 400 integration tests with an overall of around 4000 queries for any of these databases:
</p>
<ul>
<li>Azure SQL Database</li>
<li>CUBRID</li>
<li>DB2</li>
<li>Derby</li>
@ -15753,7 +15754,6 @@ Result<Record2<String, String>> result = create.select( Actor.ACTOR.FIRST_NAME,
<li>Oracle</li>
<li>PostgreSQL</li>
<li>SQLite</li>
<li>SQL Azure</li>
<li>SQL Server</li>
<li>Sybase Adaptive Server Enterprise</li>
<li>Sybase SQL Anywhere</li>

View File

@ -16180,6 +16180,7 @@ Result<Record2<String, String>> result = create.select( Actor.ACTOR.FIRST_NAME,
Every RDMBS out there has its own little specialties. jOOQ considers those specialties as much as possible, while trying to standardise the behaviour in jOOQ. In order to increase the quality of jOOQ, some 70 unit tests are run for syntax and variable binding verification, as well as some 400 integration tests with an overall of around 4000 queries for any of these databases:
</p>
<ul>
<li>Azure SQL Database</li>
<li>CUBRID</li>
<li>DB2</li>
<li>Derby</li>
@ -16195,7 +16196,6 @@ Result<Record2<String, String>> result = create.select( Actor.ACTOR.FIRST_NAME,
<li>Oracle</li>
<li>PostgreSQL</li>
<li>SQLite</li>
<li>SQL Azure</li>
<li>SQL Server</li>
<li>Sybase Adaptive Server Enterprise</li>
<li>Sybase SQL Anywhere</li>

View File

@ -16480,6 +16480,7 @@ Result<Record2<String, String>> result = create.select( Actor.ACTOR.FIRST_NAME,
Every RDMBS out there has its own little specialties. jOOQ considers those specialties as much as possible, while trying to standardise the behaviour in jOOQ. In order to increase the quality of jOOQ, some 70 unit tests are run for syntax and variable binding verification, as well as some 400 integration tests with an overall of around 4000 queries for any of these databases:
</p>
<ul>
<li>Azure SQL Database</li>
<li>CUBRID</li>
<li>DB2</li>
<li>Derby</li>
@ -16495,7 +16496,6 @@ Result<Record2<String, String>> result = create.select( Actor.ACTOR.FIRST_NAME,
<li>Oracle</li>
<li>PostgreSQL</li>
<li>SQLite</li>
<li>SQL Azure</li>
<li>SQL Server</li>
<li>Sybase Adaptive Server Enterprise</li>
<li>Sybase SQL Anywhere</li>

View File

@ -18595,6 +18595,7 @@ Result<Record2<String, String>> result = create.select( Actor.ACTOR.FIRST_NAME,
Every RDMBS out there has its own little specialties. jOOQ considers those specialties as much as possible, while trying to standardise the behaviour in jOOQ. In order to increase the quality of jOOQ, some 70 unit tests are run for syntax and variable binding verification, as well as some 400 integration tests with an overall of around 4000 queries for any of these databases:
</p>
<ul>
<li>Azure SQL Database</li>
<li>CUBRID</li>
<li>DB2</li>
<li>Derby</li>
@ -18610,7 +18611,6 @@ Result<Record2<String, String>> result = create.select( Actor.ACTOR.FIRST_NAME,
<li>Oracle</li>
<li>PostgreSQL</li>
<li>SQLite</li>
<li>SQL Azure</li>
<li>SQL Server</li>
<li>Sybase Adaptive Server Enterprise</li>
<li>Sybase SQL Anywhere</li>