Skip to content

fix: support duplicate PostgreSQL trigger names#139

Merged
DanCardin merged 1 commit into
DanCardin:mainfrom
Waszker:fix/postgresql-trigger-identity
Jun 8, 2026
Merged

fix: support duplicate PostgreSQL trigger names#139
DanCardin merged 1 commit into
DanCardin:mainfrom
Waszker:fix/postgresql-trigger-identity

Conversation

@Waszker

@Waszker Waszker commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

Closes #138

@codecov

codecov Bot commented Jun 8, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.84%. Comparing base (e820c4d) to head (b81a9d3).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #139      +/-   ##
==========================================
+ Coverage   89.83%   89.84%   +0.01%     
==========================================
  Files          86       86              
  Lines        4112     4118       +6     
  Branches      856      858       +2     
==========================================
+ Hits         3694     3700       +6     
  Misses        338      338              
  Partials       80       80              

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@DanCardin DanCardin merged commit 337665b into DanCardin:main Jun 8, 2026
19 checks passed
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.

PostgreSQL triggers with the same name on different tables are not supported

2 participants