Postgres jsonb support

[seaql]

Postgres jsonb support

[tyt2y3]

Thank you for your suggestion! We are keen to make this change. JSON support on SQL databases is a messy matter, even MySQL and MariaDB are different. We are not a day to day user of Postgres, so its nice to have your opinion!
When people use json in Postgres, do they usually use json or jsonb? I think option a) is a 'reasonable default', while b) is more explicit. I personally incline on b), but I want to know your preference as a heavy Postgres user. Speaking of that I would prefer for both json and json_binary to yield json on the MySQL side.

[Follpvosten]

"Heavy postgres user" is a bit too flattering for me, this is the first time I'm actually using it for a real project :D

I've now looked at the mariadb side and wow, that really doesn't help this case. So MariaDB's json type with a JSON_VALID check is equivalent to the postgres json type, while MySQL's new json type is equivalent to postgres jsonb.

I'm basically also just learning this myself, so for reference, here's all the info about json in postgres. In short, json is a bit cheaper on insert, but jsonb allows indexing and querying of the data, so it's more useful for data you might want to query/filter.
I would probably take the .json_binary() approach and just document that there's no difference on the mysql side (and possibly also document the difference between mariadb and mysql at that point, since mysql is technically always json_binary and mariadb is technically always json).

[tyt2y3]

thank you for your input! this sounds like a reasonable solution at this point. we will implement this change and make a new release