Jump to content

Welcome, Guest!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

  • 0
e-com

Core Updater - Database schema

Question

Using a PHP script, I converted 100% of database tables to utf8mb4_unicode_ci.
Vast majority of prestashop modules are so sloppily made, that we have all the coding from all over the world in database ๐Ÿ™‚
For what reason does Core Updater want to convert some tables back to utf8mb4_general_ci ?

ย 

Screenshot_20220925_041913.png

Link to comment
Share on other sites

3 answers to this question

Recommended Posts

  • 0

I found the cause.
In CoreModels and CMSRole classes, tables have utf8mb4_general_ci encoding declared.
Is this necessary?
Can't these tables have utf8mb4_unicode_ci encoding like rest of database?
Performance difference between utf8mb4_general_ci and utf8mb4_unicode_ci is tenths of a microsecond.

ย 

Link to comment
Share on other sites

  • 0

It's probably a good idea to unify it.

When we switched from sql installs script to ObjectModel metadata, we converted the original script. We didn't really question if it makes sense or not, the intent was to generate the exact same SQL script from object model as had in install directory.ย 

Now we can definitely think about changes ๐Ÿ™‚ย this one seems like a good one. Can you create a PR?

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


ร—
ร—
  • Create New...