Dr. Mario's 2nd 🧠

LookML terms and concepts

2 min read

rw-book-cover

Metadata

Highlights

(View Highlight)

When you generate a new project from your database, Looker creates a baseline set of files that you can use as a template for building out the project: • Multiple view files, one file for every table in the database. • One model file. The model file declares an Explore for every view. Each Explore declaration includes join logic to join any view that Looker can determine is related to the Explore. (View Highlight)

Each model can expose different data to different users. For example, sales agents need different data than company executives, and so you would probably develop two models to offer views of the database appropriate for each user. (View Highlight)

A view declaration defines a list of fields (dimensions or measures) and their linkage to an underlying table or derived table. In LookML a view typically references an underlying database table, but it can also represent a derived table. (View Highlight)

An Explore is a view that users can query. You can think of the Explore as a starting point for a query, or in SQL terms, as the FROM in a SQL statement. Not all views are Explores, because not all views describe an entity of interest (View Highlight)

The views orders and customers that are referenced within the explore declaration are defined elsewhere, in their respective view files. (View Highlight)

connection: order_database include: “filename_pattern” explore: orders { join: customers { sql_on: {customers.id} ;; } } (View Highlight)

In Looker, a set is a list that defines a group of fields that are used together (View Highlight)

used to specify which fields to display after a user drills down into data (View Highlight)

A derived table is a query whose results are used as if it were an actual table in the database (View Highlight)

Graph View