Skip to content

Update violation_info column in dolt_constraint_violations_<table> to part of PK#2329

Open
elianddb wants to merge 1 commit intomainfrom
elian/10382
Open

Update violation_info column in dolt_constraint_violations_<table> to part of PK#2329
elianddb wants to merge 1 commit intomainfrom
elian/10382

Conversation

@elianddb
Copy link
Contributor

Companion #dolthub/dolt#10497

@elianddb elianddb changed the title Update violation_info column in `dolt_constraint_violations_<table> to PK Update violation_info column in dolt_constraint_violations_<table> to part of PK Feb 14, 2026
@github-actions
Copy link
Contributor

Main PR
covering_index_scan_postgres 557.93/s 555.14/s -0.6%
index_join_postgres 118.57/s 119.71/s +0.9%
index_join_scan_postgres 173.68/s 174.20/s +0.2%
index_scan_postgres 11.08/s 10.97/s -1.0%
oltp_point_select 2252.24/s 2222.34/s -1.4%
oltp_read_only 1669.30/s 1660.10/s -0.6%
select_random_points 106.03/s 106.50/s +0.4%
select_random_ranges 418.30/s 423.72/s +1.2%
table_scan_postgres 10.87/s 10.97/s +0.9%
types_table_scan_postgres 4.98/s 4.98/s 0.0%

@github-actions
Copy link
Contributor

Main PR
Total 42090 42090
Successful 17559 17559
Failures 24531 24531
Partial Successes1 5585 5585
Main PR
Successful 41.7177% 41.7177%
Failures 58.2823% 58.2823%

Footnotes

  1. These are tests that we're marking as Successful, however they do not match the expected output in some way. This is due to small differences, such as different wording on the error messages, or the column names being incorrect while the data itself is correct.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant