Once a database connection to a running database instance is established, the Database Metadata can be imported into the Vocabulary by clicking the METADATA Import button on the database tab. Then, the class:table property of each Entity is populated with a list of the fully qualified names (catalog.schema.table or schema.table) of all tables in the database.
Typically, it is a good idea to filter the metadata to specific database catalogs and/or schema.
Note: Whether or not these settings actually do filter the list depends, in part, on the type of database used and/or the JDBC driver used. For example, Oracle JDBC drivers do not honor these filters. However, the Import Database Metadata feature does apply a second layer of filtering beyond the JDBC driver to minimize the amount of metadata imported.
The ability to map entities to fully qualified table names makes it possible to map a single Vocabulary to more than one catalog/schema provided they are all accessible through the same JDBC connection.
When tables are generated to the database, they will use the default Catalog/Schema unless you specify otherwise.
