Naming Conventions for Applications and Components
Applications and their components must follow these naming conventions:
• Names of the following objects can be 256 bytes long: Table, column, partition, procedure, procedure parameter, rule, sequence, synonym, constraint.
Names of the following objects can be 32 bytes long: Database, owner, user, group, profile, role, schema, location, event, alram, node, Forms, JoinDefs, QBFnames, Graphs, Reports.
Frame names and source files (*.osq) must be unique in the first 8 characters. Many programs, such as compilers, require the path to the source and object files.
Windows: Limit names to 8 to 12 characters maximum to avoid exceeding the 126-character Microsoft Windows command line limit. 
• The special characters _, #, $ and @ can be included in component names, except the character # cannot be included in procedure names.
• Component names must begin with an alphabetic character (A through Z) or underscore (_).
• Component names are not case sensitive.
• Table names cannot begin with "ii". These names are reserved for use by Ingres.
• Ingres database components—such as tables and views—can be specified using delimited identifiers. Delimited identifiers are surrounded by double quotes. Using delimited identifiers allows you to use special characters in object names, or to use keywords that are not otherwise legal as object names. Ingres tools components—such as applications and frames—cannot be specified with delimited identifiers. For more information on delimited identifiers, see the SQL Reference Guide.
Enterprise Access Products
For databases accessed through Enterprise Access products, component naming conventions are identical to the above. In particular:
• Names can be 1 to 32 bytes long.
Windows: Limit names to 8 to 12 characters maximum to avoid exceeding the 126-character Microsoft Windows command line limit. 
• Most names are case insensitive, regardless of the case sensitivity of the underlying database accessed through an Enterprise Access Product. Table names and some other database names can be case sensitive if the underlying DBMS supports this.
The following sections describe the application components in the order in which you encounter them as you design an application.
Last modified date: 04/03/2024