Skip to content

Add: Missing ON DELETE CASCADE Constraint #13105

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

BLasan
Copy link
Contributor

@BLasan BLasan commented May 15, 2025

No description provided.

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Copy link

coderabbitai bot commented May 15, 2025

📝 Walkthrough

Walkthrough

The change updates the SQL schema for Microsoft SQL Server by modifying the foreign key constraints on the IDN_OIDC_REQ_OBJECT_REFERENCE table. The constraints for TOKEN_ID and CODE_ID now include ON DELETE CASCADE, ensuring related records are automatically removed when referenced tokens or codes are deleted.

Changes

File(s) Change Summary
features/apimgt/org.wso2.carbon.apimgt.core.feature/src/main/resources/sql/mssql.sql Updated foreign key constraints on IDN_OIDC_REQ_OBJECT_REFERENCE for TOKEN_ID and CODE_ID to add ON DELETE CASCADE.

Sequence Diagram(s)

sequenceDiagram
    participant App
    participant DB as Database

    App->>DB: Delete from IDN_OAUTH2_ACCESS_TOKEN or IDN_OAUTH2_AUTHORIZATION_CODE
    DB-->>DB: Automatically delete related rows in IDN_OIDC_REQ_OBJECT_REFERENCE (ON DELETE CASCADE)
Loading

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.


Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
features/apimgt/org.wso2.carbon.apimgt.core.feature/src/main/resources/sql/mssql.sql (2)

1008-1009: Use explicit constraint names for maintainability
Without explicit names, SQL Server will generate system-assigned names that can vary across environments, making future drops or modifications cumbersome. Consider naming these constraints, for example:

-   FOREIGN KEY (TOKEN_ID) REFERENCES IDN_OAUTH2_ACCESS_TOKEN(TOKEN_ID) ON DELETE CASCADE,
-   FOREIGN KEY (CODE_ID)  REFERENCES IDN_OAUTH2_AUTHORIZATION_CODE(CODE_ID) ON DELETE CASCADE
+  CONSTRAINT FK_IDN_OIDC_REQ_OBJ_REF_TOKEN_ID 
+    FOREIGN KEY (TOKEN_ID) 
+    REFERENCES IDN_OAUTH2_ACCESS_TOKEN(TOKEN_ID) 
+    ON DELETE CASCADE,
+  CONSTRAINT FK_IDN_OIDC_REQ_OBJ_REF_CODE_ID 
+    FOREIGN KEY (CODE_ID) 
+    REFERENCES IDN_OAUTH2_AUTHORIZATION_CODE(CODE_ID) 
+    ON DELETE CASCADE

1008-1009: Provide migration steps for existing databases
This DDL only affects fresh installations. To apply the same cascade behavior in production schemas already deployed, you’ll need to drop the existing foreign‐key constraints and recreate them with ON DELETE CASCADE. Do you have a migration script or ALTER statements prepared for that?

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 3a896e6 and 7b3fafc.

📒 Files selected for processing (1)
  • features/apimgt/org.wso2.carbon.apimgt.core.feature/src/main/resources/sql/mssql.sql (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (6)
  • GitHub Check: build-product (2, group2)
  • GitHub Check: build-product (4, group4)
  • GitHub Check: build-product (1, group1)
  • GitHub Check: build-product (3, group3)
  • GitHub Check: build-carbon
  • GitHub Check: run-benchmark-test
🔇 Additional comments (1)
features/apimgt/org.wso2.carbon.apimgt.core.feature/src/main/resources/sql/mssql.sql (1)

1008-1009: Well done: Cascading deletes for token and code references added
Adding ON DELETE CASCADE to these foreign keys ensures related OIDC request references are cleaned up automatically when tokens or codes are removed, which matches the PR objective.

@BLasan
Copy link
Contributor Author

BLasan commented Jun 26, 2025

Hi,

Group 4 test is failing and don't cannot retrigger the build. Hence, cannot merge

Thanks & Regards,
Benura

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.

2 participants