Ryan Roden-Corrent 9d4888a772 Optimize qute://history for SQL backend. ... The old implementation was looping through the whole history list, which for SQL was selecting every row in the database. The history benchmark was taking ~2s. If this is rewritten as a specialized SQL query, the benchmark takes ~10ms, an order of magnitude faster than the original non-SQL implementation.		2017-06-19 07:44:11 -04:00
..
webengine	tests: Use pytest.param	2017-05-23 08:08:46 +02:00
webkit	Fix flake8 errors in test_history	2017-06-19 07:44:11 -04:00
test_adblock.py	Fix adblock UTF-8 test on Windows	2017-03-13 07:01:13 +01:00
test_commands.py	Finally update copyrights...	2017-05-09 21:37:03 +02:00
test_pdfjs.py	tests: relax pdfjs tests	2016-10-06 16:18:21 +02:00
test_qutescheme.py	Optimize qute://history for SQL backend.	2017-06-19 07:44:11 -04:00
test_shared.py	Finally update copyrights...	2017-05-09 21:37:03 +02:00
test_signalfilter.py	Finally update copyrights...	2017-05-09 21:37:03 +02:00
test_tab.py	Finally update copyrights...	2017-05-09 21:37:03 +02:00