BOBJ - Alias

Card Puncher Data Processing


Aliases are references to existing tables in a schema. An Alias is a table that is an exact duplicate of the original table (base table), with a different name.

Why using alias ?

You use aliases for two main reasons:

The example Beach universe contains 2 aliases; Resort_Country for Country, and Sponsor for Customer.

Another possible use of aliases is to create an alias for each table as it is inserted into the schema. You then build the schema using the alias tables, not the original base tables. You place the base tables together away from the main universe structure. This allows you to give meaningful names to tables, and prevents the need to rebuild major sections of a universe structure should a base table need to be aliased at a later stage.

Managing Alias



  • Click an alias and select Edit > Clear.


  • Menu > Tools > List of Aliases

Structure Pane

To avoid confusing base tables with aliases, you can display the alias with the name of the base table it represents in the table title as follows: Select Tools > Options > Graphics, and then select the Aliased Name check box

Discover More
Bobj Context Structure Pane
BOBJ - Context

Contexts are a collection of joins which provide a valid query path for to generate SQL. You use contexts to resolve join problems that can return too many or too few rows because of the way that...
Bobj Fan Trap Good Result
BOBJ - Fan Trap (serial many to one joins)

The fan trap in a BOBJ context. A fan trap is a join path problem returning too many rows. The original query which returned the Cartesian product for Wendy Craig, must return the following table...
Card Puncher Data Processing
BOBJ - Joins (Home)

The Joins in BOBJ. You have several approaches to creating joins in : Tracing joins manually in the schema (Drag and drop) Defining join properties directly ( Menu Select Insert > Join ) ....
Bobj Loop Structure Pane
BOBJ - Loops

in BOBJ. “multiple stars” Depending on the nature of the loop, you can resolve the loop in Designer using either an alias to break the join path, or a context to separate the two join paths...

Share this page:
Follow us:
Task Runner