Use jsonb data type for PostgreSQL to increase perfomance

[helloiamlukas]

To improve perfomance for Postgres databases, the json columns can use the jsonb data type.

This is will reduce responsetimes drastically when dealing with large datasets.

[jasonvarga]

I'm fairly sure you can just do $table->jsonb('name') without all those conditions.

On DBs that don't support jsonb, it'll fall back to json or text.

Postgres uses jsonb as expected:

https://github.com/laravel/framework/blob/ec3958de050d14f15832aa7604fb6834efa807bf/src/Illuminate/Database/Schema/Grammars/PostgresGrammar.php#L780-L783

MySQL goes to json:

https://github.com/laravel/framework/blob/ec3958de050d14f15832aa7604fb6834efa807bf/src/Illuminate/Database/Schema/Grammars/MySqlGrammar.php#L718-L721

SQLite goes to text:

https://github.com/laravel/framework/blob/ec3958de050d14f15832aa7604fb6834efa807bf/src/Illuminate/Database/Schema/Grammars/SQLiteGrammar.php#L624-L633

[what-the-diff]

• Changed the column type of settings from json to jsonb in asset containers table.
• Changed the column type of data from json to jsonb in assets meta table.
• Changed the column type of data from json to jsonb in blueprints table and added a unique index on handle and namespace columns together as they are used for querying data by both fields combined (handle,namespace).
• Same changes as above but with collections instead of blueprints: changed settings field's datatype from JSON to JSONB, also made it nullable since this is not required when creating new collection entries via API or UI; Also created an index on handle because we query based on that value alone sometimes (eager loading) - see https://github.com/statamic/cms/blob/master-v3/.github%2FISSUE_TEMPLATE%2FFEATURE_REQUEST-COLLECTION_ENTRY_INDEXES_.md#indexes .

[helloiamlukas]

Yes, you are right. I removed them now. Thanks for the hint!