Valentin Tolmer 442c70b6d2 server: Fix panic due to database collation ...

When the database's collation is not "C", the DB order is not the same as the
Rust order. As such, asserting that the elements are in increasing order fails.
However, since both queries get the order from the database, they should be in
the same order.

With too many users, the query had a giant filter `IN (u1, u2, u3,
...)`. In PostgreSQL, we can pass the users as an array instead, but that
doesn't work with SQLite. Instead, we repeat the filter from the
previous query to get the same users/groups, as a subquery.

2024-02-05 15:51:43 +00:00

..

src

server: Fix panic due to database collation

2024-02-05 15:51:43 +00:00

tests

server: Move the definition of UserId down to lldap_auth

2024-01-15 23:48:59 +01:00

Cargo.toml

server: update ldap3_proto dependency

2024-01-16 17:52:15 +01:00