JSON field type for migration erroneous
kirkbushell opened this issue · comments
Not sure why it's a json field type when json isn't being provided, but the default migration for the tags, specifies both name and slug as JSON fields.
This might work in MySQL, which is a non-standard SQL implementation, but breaks on others, such as Postgres.
Obviously this is easy to fix, as we can publish the migration and change those fields, but it still makes little sense why the migration has JSON fields for those two columns.
I also noticed that columns that -should- be indexed, aren't - as they're queried on within the package itself, namely - slug, and type.
Dear contributor,
because this issue seems to be inactive for quite some time now, I've automatically closed it. If you feel this issue deserves some attention from my human colleagues feel free to reopen it.