Skip to content

Fix: Skipping Multiple column references by a single column in Foreign Key during Index Creation #22658

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.

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

Merged
merged 2 commits into from
Jul 30, 2025

Conversation

yan-3005
Copy link
Contributor

@yan-3005 yan-3005 commented Jul 30, 2025

Describe your changes:

  1. Skipping Index for multiple column references for foreign key.
  2. If any error occurs during this , skip the current doc and proceed.
  3. Tests

I worked on ... because ...

Type of change:

  • Bug fix
  • Improvement
  • New feature
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation

Checklist:

  • I have read the CONTRIBUTING document.
  • My PR title is Fixes <issue-number>: <short explanation>
  • I have commented on my code, particularly in hard-to-understand areas.
  • For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

@yan-3005 yan-3005 self-assigned this Jul 30, 2025
@yan-3005 yan-3005 requested a review from a team as a code owner July 30, 2025 05:00
@yan-3005 yan-3005 added safe to test Add this label to run secure Github workflows on PRs backend labels Jul 30, 2025
Copy link

@yan-3005 yan-3005 merged commit b343461 into main Jul 30, 2025
23 of 27 checks passed
@yan-3005 yan-3005 deleted the table-constraint-fix-main branch July 30, 2025 15:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend safe to test Add this label to run secure Github workflows on PRs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants