COMMITS view

This Information Schema view displays a row for each instance commit which exists inside this project. A commit could be made individually for an instance or via a build. If you build a set of instances, all instances are commited at the same time with this build, the TYPE of the commit will be 'Build' instead of 'Commit' for a regular commit.

See also

• INSTANCES view

Columns

Column	Data Type	Description
PATTERN	string	The name of the pattern to which the commited instance belongs
FOLDER	string	The folder path to the instance
INSTANCE	string	The name of the instance for which the commit exists
RELEASE	string	The name of the release to which the commit belongs
USER_NAME	string	The name of the user who created the commit
TYPE	string	The type of the commit, either 'Build' or 'Commit'
STATUS	string	The status of the build if the type is 'Build'
COMMIT_TIMESTAMP	integer	The numeric unix timestamp of this commit
DELETED	integer	A flag indicating whether the instance has been deleted, 1=deleted, 0=not deleted
DESCRIPTION	string	The description of the commit

Examples

The following query retrieves all commits which exist in the the current project.

SELECT * FROM @INFORMATION_SCHEMA.COMMITS;

+-----------------+------------+--------------+-----------+-----------------+--------+----------+------------------+---------+------------------------+
| PATTERN         | FOLDER     | INSTANCE     | RELEASE   | USER_NAME       | TYPE   | STATUS   | COMMIT_TIMESTAMP | DELETED | DESCRIPTION            |
+-----------------+------------+--------------+-----------+-----------------+--------+----------+------------------+---------+------------------------+
| CORE_DATA_VAULT | /RAW_VAULT | ACCOUNT_HUB  | R.2025.Q3 | max@muster.com  | Build  | FINISHED | 1663009544003    | 0       | Re-build some entities |
| CORE_DATA_VAULT | /RAW_VAULT | CUSTOMER_SAT | R.2025.Q3 | max@muster.com  | Build  | FAILED   | 1663009530153    | 1       |                        |
| LDG_FLAT_FILE   | /SRC_A     | Acc_obj_tbl  | R.2025.Q3 | johndoe@web.com | Build  | CANCELED | 1710955659465    | 0       |                        |
| LDG_FLAT_FILE   | /SRC_B     | Partners     | R.2025.Q3 | johndoe@web.com | Commit | FINISHED | 1714162044719    | 0       | Commit partners        |
+-----------------+------------+--------------+-----------+-----------------+--------+----------+------------------+---------+------------------------+

Pattern specific commits

Each pattern in your project has its own special view, which simplifies the query for commits for a specific pattern. The view has the same structure as @INFORMATION_SCHEMA.COMMITS, but the PATTERN column is omitted. The view will be named like the pattern for which it returns the commits. You have to prefix it with @COMMITS to query it.

Examples

SELECT * FROM @COMMITS.CORE_DATA_VAULT;

+------------+--------------+-----------+-----------------+--------+----------+------------------+---------+------------------------+
| FOLDER     | INSTANCE     | RELEASE   | USER_NAME       | TYPE   | STATUS   | COMMIT_TIMESTAMP | DELETED | DESCRIPTION            |
+------------+--------------+-----------+-----------------+--------+----------+------------------+---------+------------------------+
| /RAW_VAULT | ACCOUNT_HUB  | R.2025.Q3 | max@muster.com  | Build  | FINISHED | 1663009544003    | 0       | Re-build some entities |
| /RAW_VAULT | CUSTOMER_SAT | R.2025.Q3 | max@muster.com  | Build  | FAILED   | 1663009530153    | 1       |                        |
+------------+--------------+-----------+-----------------+--------+----------+------------------+---------+------------------------+