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'm pleased to see that postgres is the default database for the recipe when installing doctrine-bundle.
JSONB has been available since postgres 9.4, released in 2014. It's hard to imagine why someone would want a larger, slower JSON column. I'd like to propose that when make:entity make it easier (or make it the default) to create JSONB columns.
The easiest way, I think, is when the type is json to always add the
It appears to not have any effect on databases that don't support it, at least SQLite. I'm not sure how MySQL handles it.
Alternatively, the maker could detect the postgres platform and prompt for jsonb.
On a related note, why is the PHP type an array rather than an object? Or both/either? Again, make:entity could add an additional type, json-object, and keep json as an array.
The text was updated successfully, but these errors were encountered:
I'm pleased to see that postgres is the default database for the recipe when installing doctrine-bundle.
JSONB has been available since postgres 9.4, released in 2014. It's hard to imagine why someone would want a larger, slower JSON column. I'd like to propose that when make:entity make it easier (or make it the default) to create JSONB columns.
The easiest way, I think, is when the type is json to always add the
It appears to not have any effect on databases that don't support it, at least SQLite. I'm not sure how MySQL handles it.
Alternatively, the maker could detect the postgres platform and prompt for jsonb.
On a related note, why is the PHP type an array rather than an object? Or both/either? Again, make:entity could add an additional type, json-object, and keep json as an array.
The text was updated successfully, but these errors were encountered: