I started adding multilingual comments in my QuickSQL definitions to support future AI-related functionality. For example:
Lookup_Types /unique LOOKUP_CODE, LANGUAGE_ISO_CODE --/* ELL:Τύποι λιστών τιμών | ENG:Lookup types /
LOOKUP_CODE vc50 /nn --/ ELL:Κωδικός λίστας | ENG:Lookup code /
LANGUAGE_ISO_CODE vc16 /nn /fk Languages --/ ELL:Γλώσσα περιγραφής | ENG:Language of description /
DESCRIPTION vc4000 --/ ELL:Περιγραφή τύπου λίστας | ENG:Lookup type description /
NOTES vc4000 --/ ELL:Σημειώσεις | ENG:Notes */
The QuickSQL file was saved as UTF-8. The content length is 27,874 characters, but the actual file size is 34,282 bytes because of the multi-byte UTF-8 characters (Greek text).
When I attempted to save the definition as a QuickSQL model, only part of the content was saved, indicating that the storage limit is based on character or byte length constraints.
It would be beneficial if the QuickSQL model definition were stored in a CLOB instead of a VARCHAR2 column. This would eliminate limitations caused by larger UTF-8 files and allow developers to include multilingual comments, metadata, and AI-related annotations without risking truncation during save operations.
I started adding multilingual comments in my QuickSQL definitions to support future AI-related functionality. For example:
Lookup_Types /unique LOOKUP_CODE, LANGUAGE_ISO_CODE --/* ELL:Τύποι λιστών τιμών | ENG:Lookup types /
LOOKUP_CODE vc50 /nn --/ ELL:Κωδικός λίστας | ENG:Lookup code /
LANGUAGE_ISO_CODE vc16 /nn /fk Languages --/ ELL:Γλώσσα περιγραφής | ENG:Language of description /
DESCRIPTION vc4000 --/ ELL:Περιγραφή τύπου λίστας | ENG:Lookup type description /
NOTES vc4000 --/ ELL:Σημειώσεις | ENG:Notes */
The QuickSQL file was saved as UTF-8. The content length is 27,874 characters, but the actual file size is 34,282 bytes because of the multi-byte UTF-8 characters (Greek text).
When I attempted to save the definition as a QuickSQL model, only part of the content was saved, indicating that the storage limit is based on character or byte length constraints.
It would be beneficial if the QuickSQL model definition were stored in a CLOB instead of a VARCHAR2 column. This would eliminate limitations caused by larger UTF-8 files and allow developers to include multilingual comments, metadata, and AI-related annotations without risking truncation during save operations.