That'd just be Postgres. When you need an schema you use a normal table, when you need arbitrary JSON data you use a JSON schema.
I could always do validation before inserting data, but that opens me up to error on my side which I'd like to avoid=)
(Though if it exists please tell me, I'd be very interested!)
One very good, which I extensively used in my previous position was DevExpress (https://www.devexpress.com/Products/NET/Controls/WPF/Editors...).
Guess again. You can use JSON functions¹ in constraints:
create table foo (
bar jsonb,
constraint bar_count_is_positive check (bar->>'count' is not null and (bar->>'count')::integer >= 0)
);
etcYou could probably write a tool pretty easily to convert a JSON schema to Postgres constraints.
1. https://www.postgresql.org/docs/current/static/functions-jso...