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 had this idea while looking for database instructions and only found this:
Finally, you should make sure that all translatable attributes are set to the text-datatype in your database. If your database supports json-columns, use that.
Wouldn't it be nice to have a command that automatically generates a new database migration that transforms all translatable fields to JSON or TEXT, based on the models $translatable fields ?
This would prevent users to have to either
manually set database field types (-> can't possibly be an acceptable solution right ?),
manually create a new migration with new field types or
manually modify existing migrations with new types and refresh DB (currently the solution I am looking at)
All of these solutions seem a little redundant to me, or am I missing an easy solution ?
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.
-
Hello !
I had this idea while looking for database instructions and only found this:
Wouldn't it be nice to have a command that automatically generates a new database migration that transforms all translatable fields to
JSON
orTEXT
, based on the models$translatable
fields ?This would prevent users to have to either
All of these solutions seem a little redundant to me, or am I missing an easy solution ?
Beta Was this translation helpful? Give feedback.
All reactions