Current implementation is similar to what you describe, but the worst
On Fri, Jan 27, 2012 at 3:49 PM, Aristotle Pagaltzis <firstname.lastname@example.org>
* Lars Lindner <email@example.com> [2012-01-26 09:40]:
> My point is mainly that the reason for choosing sqlite is gone andLast I checked it looked like Liferea loaded list views by SELECTing
> there is at least one DB backend that has much better concurrent write
every possible candidate record individually in a separate query, one
by one, then checking the result with a show-or-not predicate function
written in C. For a 100,000-entries list there are 100,000 queries
returning one row each.
I donít think SQLite is to blame for the performance issues.
(*Please* tell me I got this totally wrong.)