kolaente 0195322aab fix(db): ping the database on connect so failures report the real error ...

xorm connects lazily, so nothing touched the database until the ParadeDB probe
ran, and a connection failure surfaced as "could not check for paradedb
extension" followed by "Schema check failed: could not determine the current
schema" - which is how #3287 came in labelled as a schema bug. Ping right after
the engine is built and let the existing "Could not connect to db" callers report
it. The ParadeDB probe moves up alongside it so it no longer runs first.

2026-07-26 15:40:29 +02:00

..

fixtures

fix(security): hash password-reset, email-confirm and deletion tokens at rest (GHSA-r6w9-259g-gwrv)

2026-07-19 18:59:34 +02:00

db_path_test.go

…

db_test.go

fix(postgres): resolve all statements against the configured schema (#3156)

2026-07-11 18:02:57 +02:00

db.go

fix(db): ping the database on connect so failures report the real error

2026-07-26 15:40:29 +02:00

dump.go

fix(db): interpolate table identifiers in truncate instead of binding them

2026-06-17 12:13:50 +00:00

helpers_test.go

test: call real MultiFieldSearch function and branch on db engine

2026-03-05 13:57:05 +01:00

helpers.go

feat(search): boost title matches 1.5x over description matches

2026-07-06 15:45:55 +00:00

test_fixtures.go

…

test.go

…