Support multiple DB drivers – avoid global.__jacksonDb collision

[Reductions]

1. Background
I need to store SCIM Directory-Sync data in a dedicated “slow” database (per security/audit requirements), while all SSO-related data should live in our common, high-performance production database.

2. What I’m Trying to Do

• SSO controllers use our default setup:

  controllers({
    db: {
      engine: 'sql' as const,
      type: 'mariadb' as const,
      url: this.ssoConfiguration.DATABASE_URL,
      ttl: Duration.fromObject({ minutes: 10 }).as('seconds'),
    },
  });

• SCIM controllers use a custom driver for the slow store:

  controllers({
    db: {
      driver: customDriver,
      ttl: Duration.fromObject({ minutes: 10 }).as('seconds'),
    },
  });

• Expectation: each call to controllers({ db: … }) should isolate its own connection.

3. Current Behavior

• On the first call to controllers(...), Jackson stores the DB under global.__jacksonDb.
• Any subsequent controllers(...) invocations ignore the new db and reuse the one in global.__jacksonDb.
• There is an internal noCache flag in db.ts that’s always set to false and not exposed. Even if you override it to true, it only skips reading the existing cached DB but still writes the new instance into the cache—so it neither fully bypasses nor disables caching.

4. Why This Is a Problem

• Forces all controllers to share a single connection, making multi-tenant or multi-driver scenarios impossible.
• No way to “opt out” of the global cache.

5. What I’d Expect

• Passing a fresh db instance to controllers() should always win over any cached global.
• Optional toggle (e.g. { cacheDb: false }) or instance-scoped storage instead of global.

6. Willingness to Contribute
I’m happy to implement and submit this change (e.g. expose and respect a noCache option or similar) if it aligns with the project’s direction—just let me know the preferred approach!

[deepakprabhakara]

@Reductions Thanks. That would be great, an env config that passed noCache to the initialization of the library, uses it there and passes it down the db init (which already supports the noCache flag in the function).