-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Use regular CREATE TABLE instead of CREATE TEMPORARY #30669
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
Conversation
50cbf2d to
0b9c43f
Compare
|
rebased with main |
...cloak/connections/jpa/updater/liquibase/custom/JpaUpdate25_0_0_MySQL_ConsentConstraints.java
Show resolved
Hide resolved
I see the issue now, I missed one more DROP statement still using TEMPORARY. |
|
@pedroigor is there any other pending action from me on this? |
|
It sounds like a reasonable fix. Could you remove the merge commit to maintain a linear Git history? To do so, run: git clone --single-branch --branch patch-1 [email protected]:mike-pt/keycloak.git
cd keycloak
# Remove the merge commit from your local branch
git reset --hard HEAD~1
# Rebase your local branch onto main
git remote add upstream [email protected]:keycloak/keycloak.git
git pull --rebase upstream main
# Make sure the only commit in it is signed
git commit --amend --signoff
# Force push your local branch to remove the previously pushed merge commit by resetting the remote branch
git push --forceAdditionally, I suggest adding the following line at the end of the PR, as it hints that you haven’t overlooked this requirement in the commit message. Signed-off-by: mike-pt <[email protected]> |
Some hosted/managed environments like google CloudSQL, might not support this type of statement (i.e. when using replication and GTID) Since we are dropping the table anyway it seems a regular CREATE statement should work fine here. Signed-off-by: mike-pt <[email protected]>
|
@codespearhead recommendations addressed |
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.
Unreported flaky test detected, please review
Unreported flaky test detectedIf the flaky tests below are affected by the changes, please review and update the changes accordingly. Otherwise, a maintainer should report the flaky tests prior to merging the PR. org.keycloak.testsuite.webauthn.WebAuthnIdlessTest#testWebAuthnIDLessAndWebAuthnAndWebAuthnPasswordlessLoginKeycloak CI - WebAuthn IT (chrome) |
ahus1
left a comment
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.
LGTM, thank you for the change.
@pedroigor - are you ok if we merge this?
|
@pedroigor is there anything blocking this on my side? |
|
@pedroigor sorry for the re ping but its been a month since my last comment and I'm not sure if there is something blocking this or now? It seems it was already approved just needs to be merged in? |
|
Sorry for the delay. Thanks! |
Some hosted/managed environments like google CloudSQL, might not support this type of statement (i.e. when using replication and GTID) as seen in #30631
Since we are dropping the table anyway it seems a regular CREATE statement should work fine here.
Closes #30631
Signed-off-by: mike-pt [email protected]