Connection configuration provider - without changes to drivers #3497
…"undefined" so "null" will also be supported.
…ll DBs + removing expiryChecker from config being passed to DB drivers
…oving it (and also initializing it to null if needed) - in order to maintain a stable set of properties in the client.
…fferent for different databases, and the tests seem to be just as valid wihtout them.
@kibertoad Ok so the only open issue AFAIK is that I get a test failing on Oracle when Travis runs automatically. I can't reproduce this because when I try to run Oracle tests locally according to the instructions, I get an error (the
Actually, looking again at index.d.ts, I see there are ConnectionConfig interfaces defined for the various databases. Should I add an expiryChecker to each one?
The test is still failing:
I can't reproduce it since I'm not able to run Oracle tests, any suggestions?
P.S the TS definitions I added aren't complete, I need to add a modified connection definition too. Will add later today.
…by provider. This is currently not supported since parsing a config string is done in knex.js while the connection config provider is implemented in client.js