When the find_opt is used with a SELECT ... WHERE .. that returns more than one value, the Sqlite3 backend seems to return the first value it finds, while the postgresql backend fails with
Database-error: Unexpected result from
<postgresql://postgres:_@localhost:5432/postgres>: Received 2 tuples,
(I do prefer the PostgreSQL behavior :) which is the "production" backend in my use-case)
When the
find_opt
is used with aSELECT ... WHERE ..
that returns more than one value, the Sqlite3 backend seems to return the first value it finds, while the postgresql backend fails with(I do prefer the PostgreSQL behavior :) which is the "production" backend in my use-case)