Support table and field-level charsets and collations about laravel-migrations-generator HOT 3 CLOSED

Hi @Synchro , I am very sorry for my late reply, which took place a month ago.

By default, the generator will generate migrations without considering the DB charset/collation.

If you would like to generate migrations as you described, you need to run the generator with the option --use-db-collation.

When using this option, it will compare the DB charset/collation with your Laravel configuration.
If they matched, nothing will be changed.
Else, it will generate migrations with respect to your DB charset/collation.

Please let me know if the option doesn't work for you.

from laravel-migrations-generator.

Why wouldn't this be the default? Surely the intention is to create migrations that reflect the database schema accurately, and that would include charsets and collations? I can see that you might want to not do it as a special case, but that should be rare.

from laravel-migrations-generator.

Hi @Synchro , you raise a valid point.

However, when I started working on this project, the charset and collations were not being generated as part of the migrations.

To strike a balance between consistency and offering additional functionality, I made the decision to maintain the original behavior as the default, and I introduced the --use-db-collation option.

In summary, this allows users who want to generate migrations with respect to their database's charset and collation to do so while keeping the original behavior.

from laravel-migrations-generator.