-
Notifications
You must be signed in to change notification settings - Fork 1
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
baseapp-e2e: move to baseapp-backend #273
Conversation
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the 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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
|
sql_statements = sql_flush(style, connection) | ||
|
||
# Changing the constraints to IMMEDIATE to avoid issues with circular foreign keys like users<->profiles | ||
sql_statements = ["SET CONSTRAINTS ALL IMMEDIATE;"] + sql_statements |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had to add this SET CONSTRAINTS ALL IMMEDIATE;
to work around the pending trigger events
issue when trying to truncate all tables. Even though all tables were listed in the TRUNCATE
command it was still triggering this issue.
No description provided.