Handle SQL name limits in MySQL and SQL Server

1 files changed, 13 insertions, 8 deletions

diff --git a/NEWS b/NEWS
index 49e4aa4..ccbedde 100644
--- a/NEWS
+++ b/NEWS
@@ -36,16 +36,21 @@ Version 2.4.0
  * Support for calling MySQL stored procedures. For details and limitations
    refer to Section 17.7, "MySQL Stored Procedures" in the ODB manual.
 
- * New option, --statement-regex, can be used to process prepared statement
-   names that are used by PostgreSQL. This can be useful, for example, to
-   shorten names that exceed the PostgreSQL name limit. To this effect, ODB
-   now also warns when an SQL name exceeds the default PostgreSQL limit of
-   63 characters.
-
  * New option, --oracle-warn-truncation, makes ODB warn about SQL names
    that are longer than 30 characters and are therefore truncated. ODB
-   now also detects when such truncations lead to name conflicts and
-   issues diagnostics even without this option specified.
+   now also detects when such truncations lead to Oracle name conflicts
+   and issues diagnostics even without this option specified.
+
+ * For MySQL, PostgreSQL, and SQL Server, ODB now warns when an SQL name
+   exceeds the database limit (64, 63, and 128 characters, respectively).
+   SQLite has no limitation on name lengths. For Oracle, which has a limit
+   that is much more likely to be reached in normal circumstances (30
+   characters), a more comprehensive detection is implemented (see item
+   above).
+
+ * New option, --statement-regex, can be used to process prepared statement
+   names that are used by PostgreSQL. This can be useful, for example, to
+   shorten names that exceed the PostgreSQL name limit.
 
 Version 2.3.0