Skip to content
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

Database Optimizations #1435

Open
alexBLR opened this issue Nov 27, 2024 · 1 comment
Open

Database Optimizations #1435

alexBLR opened this issue Nov 27, 2024 · 1 comment

Comments

@alexBLR
Copy link
Contributor

alexBLR commented Nov 27, 2024

No description provided.

@alexBLR
Copy link
Contributor Author

alexBLR commented Nov 27, 2024

  • Usage of utf8mb3 charset

    The following objects use the utf8mb3 character set. We recommend that you convert them to use the utf8mb4 character set instead for improved Unicode support.
    More Information:
    https://dev.mysql.com/doc/refman/8.0/en/charset-unicode-utf8mb3.html

  • blacklight_catalog_arch2.ar_internal_metadata.key - column's default character set: utf8

  • blacklight_catalog_arch2.schema_migrations.version - column's default character set: utf8

  • Zero Date, Datetime, and Timestamp values

As of MySQL version 5.7.8, zero values for DATE, DATETIME, and TIMESTAMP data types are no longer supported. The NO_ZERO_IN_DATE and NO_ZERO_DATE modes are included in sql_mode by default. Use these modes with strict mode, as they will be merged with strict mode in a future release. If you don’t include these modes in your sql_mode setting, you can insert DATE, DATETIME, and TIMESTAMP values that contain zeros. We recommend replacing zero values with valid values, as they might not function correctly in the future.
More Information:
https://lefred.be/content/mysql-8-0-and-wrong-dates/

  • global.sql_mode - does not contain either NO_ZERO_DATE or NO_ZERO_IN_DATE which allows insertion of zero dates

  • Check for deprecated or invalid user authentication methods.

Some users are using authentication methods that may be deprecated or removed, please review the details below.
mysql.sys@localhost - The following users are using the 'mysql_native_password' authentication method which is deprecated as of MySQL 8.0.34 and will be removed in a future release.
Consider switching the users to a different authentication method (i.e. caching_sha2_password).
The 'mysql_native_password' authentication type is disabled by default in MySQL 8.4, but can still be enabled by setting loose_mysql_native_password=ON.
admin@% - The following users are using the 'mysql_native_password' authentication method which is deprecated as of MySQL 8.0.34 and will be removed in a future release.
Consider switching the users to a different authentication method (i.e. caching_sha2_password).
The 'mysql_native_password' authentication type is disabled by default in MySQL 8.4, but can still be enabled by setting loose_mysql_native_password=ON.
mysql.session@localhost - The following users are using the 'mysql_native_password' authentication method which is deprecated as of MySQL 8.0.34 and will be removed in a future release.
Consider switching the users to a different authentication method (i.e. caching_sha2_password).
The 'mysql_native_password' authentication type is disabled by default in MySQL 8.4, but can still be enabled by setting loose_mysql_native_password=ON.

@alexBLR alexBLR changed the title Database Optimization Database Optimizations Nov 27, 2024
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

No branches or pull requests

1 participant