Jean Boussier

> but I was not able to find an easy way to determine of the project uses multiple databases. I think we should do this, because I agree that when...

> Fixed to not include connection info for multiple databases. Thanks. > I would appreciate any suggestions. Yeah, I must admit I'm not super well versed in Rails vanilla multi-db...

CI failures look legit: ``` Error: DefaultScopingTest#test_default_scope_with_conditions_hash: RuntimeError: Wrapped undumpable exception for: ActiveRecord::StatementInvalid: SQLite3::BusyException: database is locked /usr/local/bundle/gems/sqlite3-1.6.9-x86_64-linux/lib/sqlite3/resultset.rb:162:in `step' /usr/local/bundle/gems/sqlite3-1.6.9-x86_64-linux/lib/sqlite3/resultset.rb:162:in `next_hash' /usr/local/bundle/gems/sqlite3-1.6.9-x86_64-linux/lib/sqlite3/resultset.rb:97:in `next' /usr/local/bundle/gems/sqlite3-1.6.9-x86_64-linux/lib/sqlite3/resultset.rb:125:in `each' ```

> I'm guessing Buildkite runs tests in parallel? Not as far as I know. However it runs test on Linux, perhaps it's not linking to the same version of sqlite3?

I modified your PR so it's enabled in the adapter by default rather than in the default generated config, as to have coverage on CI. But it's causing issues with...

The fixtures transaction uses `joinable: false`, you can probably just use that to decide on defered VS immediate.

Thanks for letting me know. I'll fix the test tomorrow.

`master-nightly-jammy` doesn't cut it? It was last built 3 hours ago: https://hub.docker.com/layers/rubylang/ruby/master-nightly-jammy/images/sha256-629a6b60bceb263049c8b6b6e48dbd637356794f481da90f7abfcd1574a57dac?context=explore

@tompng anything blocking this PR?

`coderange_scan`: this means it's crashing while trying to read the content of a String. Which means some extension created a corrupted RString (pointing to an invalid memory region). That's 100%...