Allow using custom Client/Dialect #1428
I stand to my suggested solution. Client API is really much knex version dependent. If some version of knex would change the API, the plugin-client would stop working any way. So there is no point supporting any other soft verification.
Two tests added.
As well PR #1427 merging with this PR would be welcomed.
FYI i made use of custom dialect feature. The only problem i see is a wierd way of getting ancestors: