JSON field vs plain text field

I think it's mostly for the cross-database support so that you can abstract away the problem so that data is stored appropriately regardless of which database you're using? In theory, anyway.

Also core text fields have text formats, and so a content editor could mistakenly change the text format to something like Full HTML and break the JSON.

In addition there's some very basic JSON validation provided by the module; you can't fill a json_field JSON field with non-JSON, but of course a core text field will allow you to input anything.

Automatically closed - issue fixed for 2 weeks with no activity.