json datatype vs varchar(4000) for extension ('attributes') variables in mysql and oracle
You are welcome to contribute if you can find a way to do that with Liquibase.
I do not know liquibase but will look at it.
You are welcome to contribute if you can find a way to do that with Liquibase.
I do not know liquibase but will look at it.
I understand that H2 (and sql server) do not have a json datatype while mysql (and oracle) do. To use a view that casts the varchar to json removes a lot of flexibility like indexing over JSON elements via virtual columns if one needs the content of a certain entity (like 'begin_date and 'end_date' implemented in [attributes] in the driver table for example).
Since the tables are generated anyway could the 'attributes' columns be generated as json datatype if the server is a mysql or oracle instance?