Details
-
New Feature
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
- Extend maximum object name/identifier from about 64 to 100 or 128
> give a flexibility since to short in these days.
or
> by setting length in the configuration file
make people stop using abbreviation that like alien language needed to refer another text match/mapping table which make work slower. Even windows OS has actually unlimited 1024 byte path name from 255 MAX.
New generation dont need any limitation.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Description |
- Extend maximum object name/identifier from about 64 to 255 or 100
> give a flexibility since to short in these days. or > by setting length in the configuration file - Allow concat function at a statment `SIGNAL SQLSTATE '45000' SET MESSAGE_TEXT = concat(''); ` - Current procedure/function name getter > by calling (for example) 'PRO_NAME()'' in a procedure or function like the function 'DATABASE()' > to identify each caller function name/identifier |
- Extend maximum object name/identifier from about 64 to 255 or 100
> give a flexibility since to short in these days. or > by setting length in the configuration file - Allow concat function at a statment `SIGNAL SQLSTATE '45000' SET MESSAGE_TEXT = concat(''); ` - Current procedure/function name getter > by calling (for example) 'PRO_NAME()'' in a procedure or function like the function 'DATABASE()' > to identify each caller function name/identifier - Event Schduler Trigger when right after STARTUP / right before shutdown. > not only time repeatation. but one time call for TSTARTUP and shutdown > should prepared alternative method to turn of/off switch by configuration for emergency. |
| Description |
- Extend maximum object name/identifier from about 64 to 255 or 100
> give a flexibility since to short in these days. or > by setting length in the configuration file - Allow concat function at a statment `SIGNAL SQLSTATE '45000' SET MESSAGE_TEXT = concat(''); ` - Current procedure/function name getter > by calling (for example) 'PRO_NAME()'' in a procedure or function like the function 'DATABASE()' > to identify each caller function name/identifier - Event Schduler Trigger when right after STARTUP / right before shutdown. > not only time repeatation. but one time call for TSTARTUP and shutdown > should prepared alternative method to turn of/off switch by configuration for emergency. |
- Extend maximum object name/identifier from about 64 to 255 or 100
> give a flexibility since to short in these days. or > by setting length in the configuration file - Allow concat function at a statment `SIGNAL SQLSTATE '45000' SET MESSAGE_TEXT = concat(''); ` - Current procedure/function name getter > by calling (for example) 'PRO_NAME()'' in a procedure or function like the function 'DATABASE()' > to identify each caller function name/identifier - Event Schduler Trigger when right after STARTUP / right before Shutdown. > not only time repeatation. but one time call for STARTUP and Shutdown > Should prepared alternative method to turn of/off switch by configuration for emergency. |
| Summary | Small features request | Feature request - |
| Summary | Feature request - | Feature request - Extend maximum object name/identifier |
| Description |
- Extend maximum object name/identifier from about 64 to 255 or 100
> give a flexibility since to short in these days. or > by setting length in the configuration file - Allow concat function at a statment `SIGNAL SQLSTATE '45000' SET MESSAGE_TEXT = concat(''); ` - Current procedure/function name getter > by calling (for example) 'PRO_NAME()'' in a procedure or function like the function 'DATABASE()' > to identify each caller function name/identifier - Event Schduler Trigger when right after STARTUP / right before Shutdown. > not only time repeatation. but one time call for STARTUP and Shutdown > Should prepared alternative method to turn of/off switch by configuration for emergency. |
- Extend maximum object name/identifier from about 64 to 255 or 100
> give a flexibility since to short in these days. or > by setting length in the configuration file |
| Link | This issue relates to MDEV-30644 [ MDEV-30644 ] |
| Link | This issue relates to MDEV-30645 [ MDEV-30645 ] |
| Link | This issue relates to MDEV-30643 [ MDEV-30643 ] |
| Description |
- Extend maximum object name/identifier from about 64 to 255 or 100
> give a flexibility since to short in these days. or > by setting length in the configuration file |
- Extend maximum object name/identifier from about 64 to 255 or 100
> give a flexibility since to short in these days. or > by setting length in the configuration file make people stop using abbreviation that like alien language needed to refer another text maptch table which make work slower. Even windows OS has actually unlimited 1024 byte path name from 255 MAX. New generation dont need any limitation. |
| Description |
- Extend maximum object name/identifier from about 64 to 255 or 100
> give a flexibility since to short in these days. or > by setting length in the configuration file make people stop using abbreviation that like alien language needed to refer another text maptch table which make work slower. Even windows OS has actually unlimited 1024 byte path name from 255 MAX. New generation dont need any limitation. |
- Extend maximum object name/identifier from about 64 to 255 or 100
> give a flexibility since to short in these days. or > by setting length in the configuration file make people stop using abbreviation that like alien language needed to refer another text match/mapping table which make work slower. Even windows OS has actually unlimited 1024 byte path name from 255 MAX. New generation dont need any limitation. |
| Description |
- Extend maximum object name/identifier from about 64 to 255 or 100
> give a flexibility since to short in these days. or > by setting length in the configuration file make people stop using abbreviation that like alien language needed to refer another text match/mapping table which make work slower. Even windows OS has actually unlimited 1024 byte path name from 255 MAX. New generation dont need any limitation. |
- Extend maximum object name/identifier from about 64 to 255 or 1000
> give a flexibility since to short in these days. or > by setting length in the configuration file make people stop using abbreviation that like alien language needed to refer another text match/mapping table which make work slower. Even windows OS has actually unlimited 1024 byte path name from 255 MAX. New generation dont need any limitation. |
Please keep in mind that the identifier names are being stored in some persistent data structures where there may be surprising limits. One such place are the tables mysql.innodb_index_stats and mysql.innodb_table_stats, especially when using innodb_page_size=4k. The maximum length of an identifier there is already some 4*5*64 characters, plus some delimiters /, #P#, #SP#. The filename-safe encoding can expand each utf8mb3 character up to 5 ASCII characters. To storage engines, each partition or subpartition of a table is presented as a separate table, whose name consists of up to 4 components: schema, table, partition, subpartition name. If we implement catalogs (multi-tenancy), a 5th component (catalog name) will have to be added somewhere.
| Issue Type | Task [ 3 ] | New Feature [ 2 ] |
| Link | This issue relates to MDEV-30645 [ MDEV-30645 ] |
| Link | This issue relates to MDEV-30644 [ MDEV-30644 ] |
| Link | This issue relates to MDEV-30643 [ MDEV-30643 ] |
It's not a huge task, I think, but the one where it's difficult to predict what it'll affect. Lots of places make assumptions about the max identifier length. All system tables, InnoDB data dictionary, frms, file names, protocol, perhaps, too, and lots of internal data structures. Most of the internal data structures will auto-adjust, for sure. But going from 64 to 1000 might notably affect the heap and stack usage.
| Description |
- Extend maximum object name/identifier from about 64 to 255 or 1000
> give a flexibility since to short in these days. or > by setting length in the configuration file make people stop using abbreviation that like alien language needed to refer another text match/mapping table which make work slower. Even windows OS has actually unlimited 1024 byte path name from 255 MAX. New generation dont need any limitation. |
- Extend maximum object name/identifier from about 64 to 100 or 128
> give a flexibility since to short in these days. or > by setting length in the configuration file make people stop using abbreviation that like alien language needed to refer another text match/mapping table which make work slower. Even windows OS has actually unlimited 1024 byte path name from 255 MAX. New generation dont need any limitation. |
Yes, better. I think we could try to go to a larger number first, like, 1000, and if it'll cause too many problems that we won't be able to fix, then 128 could be an option.
| Zendesk Related Tickets | 119282 |
Thanks for the feature requests. It would be quite helpful if different feature requests end up in different JIRA items. Can you edit this down to just the first feature, adjust the title (searchability helps) and put the other items in a separate ticket now.
Can you also include more information in the individually created tickets as to why and under what circumstances the feature is useful, and if other features/functions exist within the relm of the problem, why they aren't a sufficient solution.