Catalog Explorer

The Catalog Explorer is the central viewer for the Relational Model Data in your LLBLGen Pro project and the entrance point for performing actions on these elements. In v3, LLBLGen Pro has a catalog explorer which is multi-selection aware and offers a rich feature set per node through context menus. It's a very important part of the designer especially for users who want to work database-first.

The Catalog Explorer has a detail pane which opens in the central tab area of the designer, called the Catalog Details Viewer. You can open this viewer by selecting one or more nodes in the Catalog Explorer and press cntrl-shift-D or right-click on the selected nodes and select 'Show Details...'. This viewer is read-only and gives a more detailed view on various elements available in the Catalog Explorer, like type details of entity fields.

The main parts of the catalog explorer are explained below:

The Catalog Explorer

The main Catalog Explorer elements

The following main elements are available in the Catalog Explorer:

• Relational Model Data root node. This root node, which is also available in the Project Explorer, is the central hub for Relational Model Data oriented functionality like adding relational model data from a database, or adding a new Relational Data Storage container for a database.
• Relational Model Data Storage nodes. Relational Model data, be it relational model data retrieved from a relational database (database first) or generated by the designer from entity definitions (model first), is stored in Relational Model Data Storage containers, which are visible below the Relational Model Data node.
• Catalog nodes. Every populated catalog is represented by a node right below the Relational Data Storage container node it belongs to. Several databases support multiple catalogs per project. If the database doesn't support the 'catalog' concept (like Oracle), the 'Default' catalog is used as a place holder.
• Schema nodes. A populated catalog has at least one Schema. A Schema is a container for tables, views, stored procedures and the like. When the database doesn't support the 'schema' concept (like Access, MySql, Firebird), the 'Default' schema is used as a place holder
• Sequence nodes. There are two kinds of sequences: sequences stored inside a schema (like Oracle and PostgreSql use) and system sequences which are not placed inside a schema but are available through the used RDBMS, like in SQL Server.
• Table, View, Stored Procedure nodes. These nodes represent Table, View and Stored Procedure definitions in the Relational Model Data. Beneath these nodes are available: Field, Foreign Key Constraint, Unique Constraint, Parameter and Resultset nodes

Every node in the Catalog Explorer, if applicable, has a context menu which offers functionality on that node or a group of selected nodes of that same type (e.g. a selected set of table definition nodes).

The Catalog Explorer is the starting point for when you want to reverse engineer for example entity definitions from elements found in the Relational Model Data: select the elements you want to reverse engineer and right-click the elements to bring up the context menu to select the element type you want to reverse engineer the elements into. You can also right-click for example a Schema or a Catalog to bulk-reverse engineer all elements contained in these containers. All reverse engineering activity uses the Reverse Engineering Element Editor to select the elements to reverse engineer, so it's not necessary to select all tables and all views in a catalog or schema first to reverse engineer them all.