Note that all ORM fail at some point precisely because they map types - one
always find a type that isn't supported. For me a good ORM is one that let you define
additional types easily.
They also always fail at being able to define specific features of the underlying
database, like indexes.
because of the way it was possible to define my own types.
But i ended up writing spaghetti code with it, and the module itself
has code that is not easy to understand and debug.
because it's SQL with knex and JSON-schema with tv4 under the hood and this is so right.
It's also up to you to (easily with knex) build your tables, so it fixes the issue i mentioned.
Yet it isn't a full ORM - it's JSON-schema-limited all along. If you want to change the year
of a Date, it's up to your application to (new Date(person.birthday)).setFullYear(1980) and
convert it back toISOString().
a very good impression on the eyes.
to define custom types at some point, but not yet.