Skip to main content
A PawSQL integration begins with a repository change and ends with a traceable SQL quality decision. The following objects form the contract between the source platform, the pipeline, and PawSQL.

Core Concepts

Prerequisites

No special prerequisites.

Steps

Understand how the trigger event, SQL change set, integration configuration, workspace, review policy, review job, quality gate, and external run identity form the contract between the source platform, the pipeline, and PawSQL.

Review scope

Idempotency and freshness

Treat repeated delivery of the same repository event as one logical run. Use the platform event ID when available. A new head commit must invalidate the previous decision, and only the latest commit may satisfy a merge requirement.
A passing review means the SQL satisfies the active policy. It does not execute the SQL or replace business validation, change approval, or database release controls.

Expected Result

You can map any repository change to a traceable SQL quality decision through the objects described on this page.

Verification

Confirm each concept on this page maps to your platform, pipeline, and PawSQL configuration.

Prerequisites and Security

SQL Quality Gates and Feedback

Workspaces