Reference of Generated Names
When you create certain database objects (such as primary keys, check constraints, and others), they are given a default generated name which ensures that the object is unique in the database. Until you actually execute 
the database change script, the object name appears with the label <generated>, both in the Online Browser and Design Editor.
You can optionally change the <generated> name to a custom one before committing changes to the database. In this case, make sure that the custom name is unique; otherwise, the database change script will fail with an error.
Not all database objects support generated names. The following table illustrates support for generated object names across various databases.
Database kind | Primary key | Foreign key | Unique key | Check constraint | Index |
|---|---|---|---|---|---|
Access | + | + | + | + | - |
Firebird | + | + | + | + | - |
IBM DB2 | + | + | + | + | - |
IBM DB2 for i | + | + | + | + | - |
Informix | + | + | + | + | - |
MariaDB | - | + | + | - | - |
MySQL | - | + | + | - | - |
Oracle | + | + | + | + | - |
PostgreSQL | + | + | + | + | - |
Progress OpenEdge | + | + | + | + | - |
SQLite | + | + | + | - | - |
SQL Server | + | + | + | + | - |
Sybase | + | + | + | + | - |
Teradata | - | - | - | - | - |
Legend:
+ | The object name will be generated automatically; you do not need to provide a name for it. Optionally, you can override the generated name. |
- | The object name cannot be generated automatically. Before committing changes to the database, you will need to define a unique name for the object. |