It would be a pretty small ammount of data. Say... 10Mb at most. How would that be? I mean, the "switching the databases".
It would need to be transparent to the readers. How would they see the new data? On Tue, Dec 6, 2011 at 5:23 PM, Jos Groot Lipman <donts...@home.nl> wrote: > > -----Original Message----- > From: sqlite-users-boun...@sqlite.org > [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Alejandro Martínez > Sent: dinsdag 6 december 2011 19:35 > To: General Discussion of SQLite Database > Subject: [sqlite] Cache design using sqlite3... > > I'm trying to use sqlite3 as a cache layer for queries on other database. > Actually, replace an existing layer cache which is very adhoc and propietary > (and that sucks), and i'd like to replace it with something peer reviewed / > open source, etc like sqlite. > > --- > How much data are we talking here? > > Have you considered refreshing by filling a completely separate database and > just switching the databases? > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
