John Stanton-3 wrote: > Why would it not work? It is just adding an extra top level to the > index. A tried and true method.
It will work. But won't give performance benefit. And from my undestanding it will even slow down things. You can place parts of index in different DB and on different HDD thinking it will boost the performance. But the problem is that we aren't talking about multiply selects at the same time... We are talking about updating index in sqlite which is single-threaded and even under load that wouldn't give you any advantages. Moreover you're emulating part of B-Tree with that approach and making it slower and more space consumptive. So should it work as a solution? No. You have an idea why it should work? Tell me so. -- View this message in context: http://www.nabble.com/very-large-SQLite-tables-tp24201098p24222233.html Sent from the SQLite mailing list archive at Nabble.com. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
