Join Clause

JOIN Predicates are CMISQL Elements that are used in the JOIN clause of a CMISQL Query.

Remarks

The Join Clause enables you to include additional (secondary) content types in a CMISQL Query by joining them to the primary type. This allows you to retrieve and filter on properties from related types, supporting more complex queries that span multiple content types within a CMIS Repository.

A JOIN clause in CMISQL typically takes the following form:

JOIN <SecondaryType> [AS <Alias>] ON <JoinCondition>

• <SecondaryType> is the name of the secondary content type to join.
• AS <Alias> is optional and provides a short name for referencing the joined type.
• <JoinCondition> defines how the primary and secondary types are related, usually by matching object IDs.

In Grooper, the Join Clause is configured by specifying the secondary type to join, an optional alias, and the join condition. The join condition is typically set to match the cmis:objectId property of the secondary type to the cmis:objectId of the primary type, ensuring that related objects are correctly associated in the query results.

Usage Guidance

• Use the Join Clause to access properties from secondary types that are not available on the primary type.
• Assign an alias if you need to reference the joined type with a shorter or more convenient name in SELECT, WHERE, or ORDER BY clauses.
• Joins are only supported if the repository supports secondary types and the query is not in filter mode.
• The join condition is automatically constructed to match object IDs, but you may need to adjust the configuration if your repository uses a different relationship model.

Example

SELECT d.name, s.status
FROM Document AS d
JOIN Status AS s ON s.cmis:objectId = d.cmis:objectId

In this example, the Status type is joined to the Document type, allowing the query to return both the document name and its status.

---

The Join Clause is a powerful feature for building advanced queries that require information from multiple content types. Proper configuration ensures that your queries return the desired results and leverage the full capabilities of your CMIS Repository.

Properties

Name	Type		Description
Secondary Type	String	►	Specifies the secondary content type to join in this Join Clause. ConverterSecondary Type Converter The 'Secondary Type' property determines which additional (secondary) content type will be joined to the primary type in the query. Select a secondary type from the drop-down list, which includes all available secondary types in the CMIS Repository. The selected type's properties become available for selection, filtering, and sorting in the query. If the specified type does not exist or is not queryable, a validation error will be reported. Usage Use this property to include properties from a related type in your query results. Example To join a 'Status' type to a 'Document' type, set 'Secondary Type' to Status. Changing this property affects which properties and data are available from the joined type.
Alias Name	String	►	An optional alias used to refer to the joined secondary type in the query. The 'Alias Name' property allows you to define a short, convenient name for the joined secondary type. This alias can be used to qualify property names in SELECT, WHERE, and ORDER BY clauses, especially when multiple types are joined. Enter a simple string without spaces or special characters. If not specified, the secondary type's name is used by default. Usage Use an alias to distinguish between properties from different types or to simplify query syntax. Example JOIN Status AS s ON s.cmis:objectId = d.cmis:objectId Here, s is the alias for the Status type. Changing this property affects how you reference the joined type's properties in the query.

Used By

CMISQL Query