I use TW for several years now, have recently upgraded to 3.4.2 from 2.6.x, and admittedly am a bit puzzled by the excitement surrounding the move to the new storage back-end. The idea of separating files (so deleted and less frequently-used tasks are stored separately) was brilliant in my opinion. With all being in one sqlite database now, all operations are dramatically slower, and synchronizing devices requires moving a large file back and forth.
I wonder if there is anything I'm missing here? Has it been considered to have multiple sqlite files, so to replicate the benefits of the previous storage model?
I use TW for several years now, have recently upgraded to 3.4.2 from 2.6.x, and admittedly am a bit puzzled by the excitement surrounding the move to the new storage back-end. The idea of separating files (so deleted and less frequently-used tasks are stored separately) was brilliant in my opinion. With all being in one sqlite database now, all operations are dramatically slower, and synchronizing devices requires moving a large file back and forth.
I wonder if there is anything I'm missing here? Has it been considered to have multiple sqlite files, so to replicate the benefits of the previous storage model?