Repository navigation
Release v1.17.0
v1.17.0
Changelog
Added
- Sessions:
sessions.doctrine.exact_owner_collation(defaultfalse). On a host whoseuser_kit_sessionowner
columns already carry the binary NO PAD collation of UPGRADING,
the SQL owner match is byte-exact, so the session list stops reading candidate ids through DBAL and filtering them in
PHP: it reads the rows in one query. Measured on a signed-in "My sessions" request, the registry goes from three
queries to two (revocation state, candidate scan, entities → revocation state, entities). The PHP===re-check
runs in both paths, so the option is fail-closed: turned on while the column still folds, the look-alike rows SQL
returns are dropped and the user is signed out instead of matched to someone else's session. No auto-detection: the
information_schemalookup that would replace the option costs one round trip per connection, which on a
request-per-connection host (PHP-FPM) is exactly the query it saves.
What's Changed
- feat(sessions): opt-in exact owner collation saves one query per session list by @HecFranco in #53
Full Changelog: v1.16.3...v1.17.0