Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update dolt_verify_constraints() stored procedure to support all constraint types #2093

Merged
merged 1 commit into from
Apr 3, 2024
Merged

Update dolt_verify_constraints() stored procedure to support all constraint types #2093

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
13 changes: 6 additions & 7 deletions content/reference/sql/version-control/dolt-sql-procedures.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1400,8 +1400,7 @@ SELECT * FROM database1.t;
## `DOLT_VERIFY_CONSTRAINTS()`

Verifies that working set changes (inserts, updates, and/or deletes) satisfy the
defined table constraints. Currently, the command only verifies foreign key
constraints. If any constraints are violated they are written to the
defined table constraints. If any constraints are violated they are written to the
[DOLT_CONSTRAINT_VIOLATIONS](./dolt-system-tables.md#doltconstraintviolations) table.

`DOLT_VERIFY_CONSTRAINTS` by default does not detect constraints for row changes
Expand All @@ -1425,11 +1424,11 @@ system table.
### Output Schema

```text
+------------+------+----------------------+
| Field | Type | Description |
+------------+------+----------------------+
| violations | int | number of violations |
+------------+------+----------------------+
+------------+------+-----------------------------------------+
| Field | Type | Description |
+------------+------+-----------------------------------------+
| violations | int | 1 if violations were found, otherwise 0 |
+------------+------+-----------------------------------------+
```

### Example
Expand Down