Support ‘unknown’ columns

[jellelicht]

Issue type:

• Question

Would it be possible to support columns that are ‘unknown’ to typed-knex? That is to say, columns in the db that are not a part of the typed-knex @table decorated entity. I’m thinking of a nullable column that is automatically managed by a db trigger, that shouldn’t impact any application operation in the first place.

If you are not against such a feature, would you be open to a PR implementing it as an opt-in feature?

[wwwouter]

Can you give an example as how to use it? Will it be only for select queries?