From 95c664a46668dd4f19d237e6aa6c53ffb0a2a19f Mon Sep 17 00:00:00 2001 From: lukaseder Date: Tue, 31 Jul 2018 10:34:00 +0200 Subject: [PATCH] [#7707] Dead link to MySQL manual on group by page --- .../resources/org/jooq/web/manual-2.6.xml | 16 ---------------- .../resources/org/jooq/web/manual-3.0.xml | 16 ---------------- .../resources/org/jooq/web/manual-3.1.xml | 16 ---------------- .../resources/org/jooq/web/manual-3.10.xml | 19 ------------------- .../resources/org/jooq/web/manual-3.11.xml | 19 ------------------- .../resources/org/jooq/web/manual-3.12.xml | 19 ------------------- .../resources/org/jooq/web/manual-3.2.xml | 17 ----------------- .../resources/org/jooq/web/manual-3.3.xml | 17 ----------------- .../resources/org/jooq/web/manual-3.4.xml | 19 ------------------- .../resources/org/jooq/web/manual-3.5.xml | 19 ------------------- .../resources/org/jooq/web/manual-3.6.xml | 19 ------------------- .../resources/org/jooq/web/manual-3.7.xml | 19 ------------------- .../resources/org/jooq/web/manual-3.8.xml | 19 ------------------- .../resources/org/jooq/web/manual-3.9.xml | 19 ------------------- 14 files changed, 253 deletions(-) diff --git a/jOOQ-manual/src/main/resources/org/jooq/web/manual-2.6.xml b/jOOQ-manual/src/main/resources/org/jooq/web/manual-2.6.xml index 02196acbf1..cb3d58d9b8 100644 --- a/jOOQ-manual/src/main/resources/org/jooq/web/manual-2.6.xml +++ b/jOOQ-manual/src/main/resources/org/jooq/web/manual-2.6.xml @@ -1944,22 +1944,6 @@ GROUP BY AUTHOR_ID]]>. The above example counts all books per author

-

MySQL's deviation from the SQL standard

-

- MySQL has a peculiar way of not adhering to this standard behaviour. This is documented in the MySQL manual. In short, with MySQL, you can also project any other field that are not part of the GROUP BY clause. The projected values will just be arbitrary values from within the group. You cannot rely on any ordering. For example: -

- - - - -

- This will return an arbitrary title per author. jOOQ supports this syntax, as jOOQ is not doing any checks internally, about the consistence of tables/fields/functions that you provide it. -

-

Empty GROUP BY clauses

jOOQ supports empty GROUP BY () clauses as well. This will result in that return only one record. diff --git a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.0.xml b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.0.xml index 26eb429675..a3c02fd793 100644 --- a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.0.xml +++ b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.0.xml @@ -2623,22 +2623,6 @@ GROUP BY AUTHOR_ID]]>.

-

MySQL's deviation from the SQL standard

-

- MySQL has a peculiar way of not adhering to this standard behaviour. This is documented in the MySQL manual. In short, with MySQL, you can also project any other field that is not part of the GROUP BY clause. The projected values will just be arbitrary values from within the group. You cannot rely on any ordering. For example: -

- - - - -

- This will return an arbitrary title per author. jOOQ supports this syntax, as jOOQ is not doing any checks internally, about the consistence of tables/fields/functions that you provide it. -

-

Empty GROUP BY clauses

jOOQ supports empty GROUP BY () clause as well. This will result in that return only one record. diff --git a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.1.xml b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.1.xml index 29b27456a3..e92da431ea 100644 --- a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.1.xml +++ b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.1.xml @@ -3001,22 +3001,6 @@ GROUP BY AUTHOR_ID]]>.

-

MySQL's deviation from the SQL standard

-

- MySQL has a peculiar way of not adhering to this standard behaviour. This is documented in the MySQL manual. In short, with MySQL, you can also project any other field that is not part of the GROUP BY clause. The projected values will just be arbitrary values from within the group. You cannot rely on any ordering. For example: -

- - - - -

- This will return an arbitrary title per author. jOOQ supports this syntax, as jOOQ is not doing any checks internally, about the consistence of tables/fields/functions that you provide it. -

-

Empty GROUP BY clauses

jOOQ supports empty GROUP BY () clause as well. This will result in that return only one record. diff --git a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.10.xml b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.10.xml index 22ed7857fd..cf42ad6634 100644 --- a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.10.xml +++ b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.10.xml @@ -5004,25 +5004,6 @@ GROUP BY AUTHOR_ID Note, as defined in the SQL standard, when grouping, you may no longer project any columns that are not a formal part of the GROUP BY clause, or .

-

MySQL's deviation from the SQL standard

-

- MySQL has a peculiar way of not adhering to this standard behaviour. This is documented in the MySQL manual. In short, with MySQL, you can also project any other field that is not part of the GROUP BY clause. The projected values will just be arbitrary values from within the group. You cannot rely on any ordering. For example: -

- - -  - - -

- This will return an arbitrary title per author. jOOQ supports this syntax, as jOOQ is not doing any checks internally, about the consistence of tables/fields/functions that you provide it. -

-

Empty GROUP BY clauses

jOOQ supports empty GROUP BY () clause as well. This will result in that return only one record. diff --git a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.11.xml b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.11.xml index 77f1046c8e..1bbe53d60e 100644 --- a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.11.xml +++ b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.11.xml @@ -5148,25 +5148,6 @@ GROUP BY AUTHOR_ID Note, as defined in the SQL standard, when grouping, you may no longer project any columns that are not a formal part of the GROUP BY clause, or .

-

MySQL's deviation from the SQL standard

-

- MySQL has a peculiar way of not adhering to this standard behaviour. This is documented in the MySQL manual. In short, with MySQL, you can also project any other field that is not part of the GROUP BY clause. The projected values will just be arbitrary values from within the group. You cannot rely on any ordering. For example: -

- - -  - - -

- This will return an arbitrary title per author. jOOQ supports this syntax, as jOOQ is not doing any checks internally, about the consistence of tables/fields/functions that you provide it. -

-

Empty GROUP BY clauses

jOOQ supports empty GROUP BY () clause as well. This will result in that return only one record. diff --git a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.12.xml b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.12.xml index 2c5aabf378..581e1827b3 100644 --- a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.12.xml +++ b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.12.xml @@ -5162,25 +5162,6 @@ GROUP BY AUTHOR_ID Note, as defined in the SQL standard, when grouping, you may no longer project any columns that are not a formal part of the GROUP BY clause, or .

-

MySQL's deviation from the SQL standard

-

- MySQL has a peculiar way of not adhering to this standard behaviour. This is documented in the MySQL manual. In short, with MySQL, you can also project any other field that is not part of the GROUP BY clause. The projected values will just be arbitrary values from within the group. You cannot rely on any ordering. For example: -

- - -  - - -

- This will return an arbitrary title per author. jOOQ supports this syntax, as jOOQ is not doing any checks internally, about the consistence of tables/fields/functions that you provide it. -

-

Empty GROUP BY clauses

jOOQ supports empty GROUP BY () clause as well. This will result in that return only one record. diff --git a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.2.xml b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.2.xml index 7b585a9619..34d57b9e9c 100644 --- a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.2.xml +++ b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.2.xml @@ -3116,23 +3116,6 @@ GROUP BY AUTHOR_ID]]> Note, as defined in the SQL standard, when grouping, you may no longer project any columns that are not a formal part of the GROUP BY clause, or .

-

MySQL's deviation from the SQL standard

-

- MySQL has a peculiar way of not adhering to this standard behaviour. This is documented in the MySQL manual. In short, with MySQL, you can also project any other field that is not part of the GROUP BY clause. The projected values will just be arbitrary values from within the group. You cannot rely on any ordering. For example: -

- - - - - -

- This will return an arbitrary title per author. jOOQ supports this syntax, as jOOQ is not doing any checks internally, about the consistence of tables/fields/functions that you provide it. -

-

Empty GROUP BY clauses

jOOQ supports empty GROUP BY () clause as well. This will result in that return only one record. diff --git a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.3.xml b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.3.xml index 204e95daec..f4ae16ae7c 100644 --- a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.3.xml +++ b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.3.xml @@ -3639,23 +3639,6 @@ GROUP BY AUTHOR_ID]]> Note, as defined in the SQL standard, when grouping, you may no longer project any columns that are not a formal part of the GROUP BY clause, or .

-

MySQL's deviation from the SQL standard

-

- MySQL has a peculiar way of not adhering to this standard behaviour. This is documented in the MySQL manual. In short, with MySQL, you can also project any other field that is not part of the GROUP BY clause. The projected values will just be arbitrary values from within the group. You cannot rely on any ordering. For example: -

- - - - - -

- This will return an arbitrary title per author. jOOQ supports this syntax, as jOOQ is not doing any checks internally, about the consistence of tables/fields/functions that you provide it. -

-

Empty GROUP BY clauses

jOOQ supports empty GROUP BY () clause as well. This will result in that return only one record. diff --git a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.4.xml b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.4.xml index 6afccef65a..7987200bec 100644 --- a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.4.xml +++ b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.4.xml @@ -4378,25 +4378,6 @@ GROUP BY AUTHOR_ID Note, as defined in the SQL standard, when grouping, you may no longer project any columns that are not a formal part of the GROUP BY clause, or .

-

MySQL's deviation from the SQL standard

-

- MySQL has a peculiar way of not adhering to this standard behaviour. This is documented in the MySQL manual. In short, with MySQL, you can also project any other field that is not part of the GROUP BY clause. The projected values will just be arbitrary values from within the group. You cannot rely on any ordering. For example: -

- - -  - - -

- This will return an arbitrary title per author. jOOQ supports this syntax, as jOOQ is not doing any checks internally, about the consistence of tables/fields/functions that you provide it. -

-

Empty GROUP BY clauses

jOOQ supports empty GROUP BY () clause as well. This will result in that return only one record. diff --git a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.5.xml b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.5.xml index 4fe45533e0..c1e3556d6a 100644 --- a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.5.xml +++ b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.5.xml @@ -4582,25 +4582,6 @@ GROUP BY AUTHOR_ID Note, as defined in the SQL standard, when grouping, you may no longer project any columns that are not a formal part of the GROUP BY clause, or .

-

MySQL's deviation from the SQL standard

-

- MySQL has a peculiar way of not adhering to this standard behaviour. This is documented in the MySQL manual. In short, with MySQL, you can also project any other field that is not part of the GROUP BY clause. The projected values will just be arbitrary values from within the group. You cannot rely on any ordering. For example: -

- - -  - - -

- This will return an arbitrary title per author. jOOQ supports this syntax, as jOOQ is not doing any checks internally, about the consistence of tables/fields/functions that you provide it. -

-

Empty GROUP BY clauses

jOOQ supports empty GROUP BY () clause as well. This will result in that return only one record. diff --git a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.6.xml b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.6.xml index c0a8e24f37..fb045ba34f 100644 --- a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.6.xml +++ b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.6.xml @@ -4587,25 +4587,6 @@ GROUP BY AUTHOR_ID Note, as defined in the SQL standard, when grouping, you may no longer project any columns that are not a formal part of the GROUP BY clause, or .

-

MySQL's deviation from the SQL standard

-

- MySQL has a peculiar way of not adhering to this standard behaviour. This is documented in the MySQL manual. In short, with MySQL, you can also project any other field that is not part of the GROUP BY clause. The projected values will just be arbitrary values from within the group. You cannot rely on any ordering. For example: -

- - -  - - -

- This will return an arbitrary title per author. jOOQ supports this syntax, as jOOQ is not doing any checks internally, about the consistence of tables/fields/functions that you provide it. -

-

Empty GROUP BY clauses

jOOQ supports empty GROUP BY () clause as well. This will result in that return only one record. diff --git a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.7.xml b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.7.xml index 4be414c87b..ee2830f0d4 100644 --- a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.7.xml +++ b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.7.xml @@ -4797,25 +4797,6 @@ GROUP BY AUTHOR_ID Note, as defined in the SQL standard, when grouping, you may no longer project any columns that are not a formal part of the GROUP BY clause, or .

-

MySQL's deviation from the SQL standard

-

- MySQL has a peculiar way of not adhering to this standard behaviour. This is documented in the MySQL manual. In short, with MySQL, you can also project any other field that is not part of the GROUP BY clause. The projected values will just be arbitrary values from within the group. You cannot rely on any ordering. For example: -

- - -  - - -

- This will return an arbitrary title per author. jOOQ supports this syntax, as jOOQ is not doing any checks internally, about the consistence of tables/fields/functions that you provide it. -

-

Empty GROUP BY clauses

jOOQ supports empty GROUP BY () clause as well. This will result in that return only one record. diff --git a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.8.xml b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.8.xml index b769c82277..4154095345 100644 --- a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.8.xml +++ b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.8.xml @@ -4923,25 +4923,6 @@ GROUP BY AUTHOR_ID Note, as defined in the SQL standard, when grouping, you may no longer project any columns that are not a formal part of the GROUP BY clause, or .

-

MySQL's deviation from the SQL standard

-

- MySQL has a peculiar way of not adhering to this standard behaviour. This is documented in the MySQL manual. In short, with MySQL, you can also project any other field that is not part of the GROUP BY clause. The projected values will just be arbitrary values from within the group. You cannot rely on any ordering. For example: -

- - -  - - -

- This will return an arbitrary title per author. jOOQ supports this syntax, as jOOQ is not doing any checks internally, about the consistence of tables/fields/functions that you provide it. -

-

Empty GROUP BY clauses

jOOQ supports empty GROUP BY () clause as well. This will result in that return only one record. diff --git a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.9.xml b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.9.xml index f2b479b304..bfb78ad2d3 100644 --- a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.9.xml +++ b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.9.xml @@ -5004,25 +5004,6 @@ GROUP BY AUTHOR_ID Note, as defined in the SQL standard, when grouping, you may no longer project any columns that are not a formal part of the GROUP BY clause, or .

-

MySQL's deviation from the SQL standard

-

- MySQL has a peculiar way of not adhering to this standard behaviour. This is documented in the MySQL manual. In short, with MySQL, you can also project any other field that is not part of the GROUP BY clause. The projected values will just be arbitrary values from within the group. You cannot rely on any ordering. For example: -

- - -  - - -

- This will return an arbitrary title per author. jOOQ supports this syntax, as jOOQ is not doing any checks internally, about the consistence of tables/fields/functions that you provide it. -

-

Empty GROUP BY clauses

jOOQ supports empty GROUP BY () clause as well. This will result in that return only one record.