Search

Query Language (CQL)

CDS QL is based on standard SQL, which it enhances by…

Postfix Projections

CQL allows to put projections, i.e. the SELECT clause, behind the FROM clause enclosed in curly-braces. For example, the following are equivalent:

SELECT name, address.street from Authors;
SELECT from Authors { name, address.street };

Smart * Selector

Within postfix projections, the * operator queries are handled slightly different than in plain SQL select clauses.

Example:

SELECT from Books { *, author.name as author }

Queries like in our example, would result in duplicate element effects for author in SQL, while in CQL explicitly defined columns following a * will replace equally named columns inferred before.

Path Expressions

Use path expressions to navigate along associations and/or struct elements in any of the SQL clauses as follows.

  • in from clauses:
    SELECT from Authors[name='Emily Brontë'].books;
    SELECT from Books:authors.towns;
    
  • in select clauses:
    SELECT title, author.name from Books;
    SELECT *, author.address.town.name from Books;
    
  • in where clauses:
    SELECT from Books where author.name='Emily Brontë';
    
  • and so forth for group by, having, order by.

Path Expressions in from Clauses

Path expressions in from clauses allow to fetch only those entries from a target entity, which are associated to a parent entity. They unfold to SEMI JOINS in plain SQL queries. For example, the above queries would unfold to the following plain SQL counterparts:

SELECT * from Books WHERE EXISTS (
  SELECT 1 from Authors WHERE Authors.ID = Books.author_ID
    AND Authors.name='Emily Brontë'
);
SELECT * from Towns WHERE EXISTS (
  SELECT 1 from Authors WHERE Authors.town_ID = Towns.ID AND EXISTS (
    SELECT 1 from Books WHERE Books.author_ID = Authors.ID
  )
);

Path Expressions in All Other Clauses

Path expressions in all other clauses are very much like standard SQL’s column expressions with table aliases as single prefixes. CQL essentially extends the standard behavior to paths with multiple prefixes, each resolving to a table alias from a corresponding LEFT OUTER JOIN. For example, the path expressions in the above queries would unfold to the following plain SQL queries:

SELECT Books.title, author.name from Books
LEFT JOIN Authors author ON author.ID = Books.author_ID;
SELECT Books.*, author_address_town.name from Books
LEFT JOIN Authors author ON author.ID = Books.author_ID
LEFT JOIN Addresses author_address ON author_address.ID = author.address_ID
LEFT JOIN Towns author_address_town ON author_address_town.ID = author_address.town_ID;
SELECT Books.* from Books
LEFT JOIN Authors author ON author.ID = Books.author_ID
WHERE author.name='Emily Brontë'

Note that all column references get qualified → in contrast to plain SQL joins there is no risk of ambiguous or conflicting column names.

With Infix Filters

Append infix filters to associations in path expressions to narrow the resulting joins. For example:

SELECT books[genre='Mystery'].title from Authors
 WHERE name='Agatha Christie'

… unfolds to:

SELECT books.title from Authors
LEFT JOIN Books books ON ( books.author_ID = Authors.ID )
  AND ( books.genre = 'Mystery' )  --> from Infix Filter
WHERE Authors.name='Agatha Christie';

CDL-style Casts

Instead of SQL-style type casts you can alternatively use CDL-style casts, i.e. as in the element of an entity definitions. For example, the following statements are equivalent:

SELECT cast (foo+1 as Decimal) as bar from Foo;  -- standard SQL
SELECT from Foo { foo+1 as bar : Decimal };      -- CDL-style

learn more about CDL type definitions

SQL-style type casts are not yet supported.

Excluding Clause

Use the excluding clause in combination with SELECT * to select all elements except for the ones listed in the exclude list.

SELECT from Books { * } excluding { author };
SELECT from Books { *, author.name as author, author{*} }
excluding { author.town };

The effect is about late materialization of signatures and staying open to late extensions. For example assume the following definitions:

entity Foo { foo : String; bar : String; car : String; }
entity Bar as SELECT from Foo excluding { bar }
entity Boo as SELECT from Foo { foo, car }

A SELECT * from Bar would result into the same as a query of Boo:

SELECT * from Bar --> { foo, car }
SELECT * from Boo --> { foo, car }

Now, assume a consumer of that package extends the definitions as follows:

extend Foo with { boo : String; }

With that, queries on Bar and Boo would return different results:

SELECT * from Bar --> { foo, car, boo }
SELECT * from Boo --> { foo, car }

Query-local Mixins

Use the mixin...into clause to logically add unmanaged associations to the source of the query, which you can use and propagate in the query’s projection. This is only supported in postfix notation.

SELECT from Books mixin {
  localized : Association to LocalizedBooks on localized.ID = ID;
} into {
  ID, localized.title
};