Hey folks, I am presently working on implementing non transactional postgres implementation using jdbc. in the course of that i noticed in the entity table that the column type of the properties / internal properties column is TEXT and not JSONB, I dug a bit into the history of this, seems like we did wanted to have JSONB but ended up implementing it as TEXT (may to support more relational DB's which doesn't support JSONB) .
JSONB has a couple of benefits, some of the noticeable ones are that it lets you define indexes on them [1], which would help us in supporting some different query patterns as we start supporting new entities. Until the separate table per entity discussion is finalized, this could be helpful as with supporting the new query pattern. For ex policy need to presently do client side filtering as policyType which is a present inside properties, it needs to be parsed in client side and then do filtering at client end. Please let me know your thoughts considering the above, happy to put out a PR for the same. I am happy to handle this in my JDBC impl as this is anyway a user would be consciously choosing it over eclipse impl. I would love to know your thoughts if we need to handle it in eclipse link impl as well. Best, Prashant [1] https://scalegrid.io/blog/using-jsonb-in-postgresql-how-to-effectively-store-index-json-data-in-postgresql/
