diff options
author | Boris Kolpackov <boris@codesynthesis.com> | 2015-01-23 11:40:58 +0200 |
---|---|---|
committer | Boris Kolpackov <boris@codesynthesis.com> | 2015-01-23 11:40:58 +0200 |
commit | 465a4467adec94bb8fe996732ea378664fcf5e86 (patch) | |
tree | 23cb2f439313c73d4baaded034e1196eaf7c4f9b /NEWS | |
parent | 4701df22146e4e4fc0c7fe58903fbd0482defcb5 (diff) |
Handle SQL name limits in MySQL and SQL Server
Diffstat (limited to 'NEWS')
-rw-r--r-- | NEWS | 21 |
1 files changed, 13 insertions, 8 deletions
@@ -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 |