You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just upgraded my MySQL 8.0 instance to MySQL 8.4, and there were these warnings in the log:
hydra_dev.hydra_oauth2_access_client_id_fk - invalid foreign key defined as 'hydra_oauth2_access(nid)' references a non unique key at table 'hydra_client'.
hydra_dev.hydra_oauth2_code_client_id_fk - invalid foreign key defined as 'hydra_oauth2_code(nid)' references a non unique key at table 'hydra_client'.
hydra_dev.hydra_oauth2_flow_client_id_fk - invalid foreign key defined as 'hydra_oauth2_flow(nid)' references a non unique key at table 'hydra_client'.
hydra_dev.hydra_oauth2_logout_request_client_id_fk - invalid foreign key defined as 'hydra_oauth2_logout_request(nid)' references a non unique key at table 'hydra_client'.
hydra_dev.hydra_oauth2_obfuscated_authentication_session_client_id_fk - invalid foreign key defined as 'hydra_oauth2_obfuscated_authentication_session(nid)' references a non unique key at table 'hydra_client'.
hydra_dev.hydra_oauth2_oidc_client_id_fk - invalid foreign key defined as 'hydra_oauth2_oidc(nid)' references a non unique key at table 'hydra_client'.
hydra_dev.hydra_oauth2_pkce_client_id_fk - invalid foreign key defined as 'hydra_oauth2_pkce(nid)' references a non unique key at table 'hydra_client'.
hydra_dev.hydra_oauth2_refresh_client_id_fk - invalid foreign key defined as 'hydra_oauth2_refresh(nid)' references a non unique key at table 'hydra_client'.
hydra_dev.hydra_oauth2_trusted_jwt_bearer_issuer_ibfk_1 - invalid foreign key defined as 'hydra_oauth2_trusted_jwt_bearer_issuer(key_id,key_set,nid)' references a non unique key at table 'hydra_jwk'.
While I can disable restrict_fk_on_non_standard_key for now, I thought it worth mentioning. I'm not sure if it's been addressed in the latest Hydra?
The MySQL community has deprecated the ability to use non-unique or partial keys as foreign keys while creating or altering a table, and will remove it in a future version. To manage this transition, MySQL 8.4 includes a new parameter, called restrict_fk_on_non_standard_key, which is set to ON by default. This setting prevents the use of non-unique or partial keys as foreign keys. You can revert to the previous behavior by setting it to OFF. However, we recommend following best practices, and modifying your schema to only use unique keys as foreign keys.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I am (still) running Hydra 2.3.0.
I just upgraded my MySQL 8.0 instance to MySQL 8.4, and there were these warnings in the log:
While I can disable
restrict_fk_on_non_standard_keyfor now, I thought it worth mentioning. I'm not sure if it's been addressed in the latest Hydra?See https://aws.amazon.com/blogs/database/amazon-rds-for-mysql-lts-version-8-4-is-now-generally-available/#:~:text=Restricted%20use%20of%20non%2Dunique%20keys%20or%20partial%20keys%20as%20foreign%20keys
Beta Was this translation helpful? Give feedback.
All reactions