firebird-automations
commented
6 years ago Commented by: Sean Leyne (seanleyne)
I don't think it is necessary to report the number of characters that the length exceeds by, the message details should make that obvious.
As for the text of the error message, something more like this would read better: Length name of {Object Type} "{Object Name}" ({Length value}) exceeds maximum of {Max Length},
Eg: Length name of Table "VERY_VERY_LONGEST_NAME_OF_TABLE1" (32) exceeds maximum of 31
Submitted by: Maxim Kuzmin (cybermax)
Votes: 2
When creating various object of database and length thier names exceeding maximal, get error.
Example for package: CREATE OR ALTER PACKAGE VERY_VERY_LONGEST_NAME_OF_PACKAGE AS BEGIN
END
Invalid token. Dynamic SQL Error. SQL error code = -104. Name longer than database column size.
Example for table: CREATE TABLE VERY_VERY_LONGEST_NAME_OF_TABLE1 ( NEW_FIELD INTEGER)
Invalid token. Dynamic SQL Error. SQL error code = -104. Name longer than database column size.
Example for exception: CREATE EXCEPTION VERY_VERY_LONGEST_NAME_OF_EXCEPTION
Invalid token. Dynamic SQL Error. SQL error code = -104. Name longer than database column size.
From the message, neither the object type, nor its name, nor its actual length is understood. Sometimes, in executing script or other work, it's causes inconvenience. Propose extending error message like this:
Invalid token. Dynamic SQL Error. SQL error code = -104. Name longer than database column size. Length name of package "VERY_VERY_LONGEST_NAME_OF_PACKAGE" exceed maximum 31 chars on 2 (fact 33);
Invalid token. Dynamic SQL Error. SQL error code = -104. Name longer than database column size. Length name of table "VERY_VERY_LONGEST_NAME_OF_TABLE1" exceed maximum 31 chars on 1 (fact 32);