Repository navigation
Use regular CREATE TABLE instead of CREATE TEMPORARY - #30669
Conversation
50cbf2d to
0b9c43f
Compare
|
rebased with main |
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: Additionally, 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. |
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 <mike-pt@users.noreply.github.com>
|
@codespearhead recommendations addressed |
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) |
There was a problem hiding this comment.
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 mike-pt@users.noreply.github.com