How does Firebird's result set cache behave under READ COMMITTED isolation when concurrent updates occur?
In a Firebird 3.0 database, a table is subject to frequent UPDATE and INSERT statements from several concurrent sessions. A reporting session repeatedly executes the same SELECT statement under the READ COMMITTED isolation level, expecting to see the latest committed changes after each transaction completes. Occasionally the query returns rows that reflect a
firebird