Hello Hayden, If I was doing this, I'd use a single database as the core then periodically from within the app, write out a new database with the last 5 minutes worth of data. Then let them run off the copy while you maintain a master copy of the DB. In that way this splitting and multiple DB thing can go away while you still give them access to the data without letting them touch the master. If they need to read the master, I'd probably write a little client/server application to let them look at but, not change the data (assuming that's a requirement).
I'd avoid multiple databases with the core data like the plague. Obviously you can't always do it but, I see it as a positive design goal. C Saturday, May 3, 2014, 9:40:37 AM, you wrote: HL> This looks promising. I sooo wish it didn't have a limit to number of HL> databases. But I think I could reasonably do something like coalesce the HL> databases into a new database once every 2 hours. I also need to generate HL> some code to figure out how to address the tables which I guess means I'll HL> have to do an N way JOIN? HL> On Sat, May 3, 2014 at 6:16 AM, Petite Abeille <petite.abei...@gmail.com>wrote: >> >> On May 3, 2014, at 2:59 PM, Hayden Livingston <halivings...@gmail.com> >> wrote: >> >> > Thoughts? >> >> Take a look at ‘ATTACH’, it might help: >> >> http://www.sqlite.org/lang_attach.html >> >> _______________________________________________ >> sqlite-users mailing list >> sqlite-users@sqlite.org >> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users >> HL> _______________________________________________ HL> sqlite-users mailing list HL> sqlite-users@sqlite.org HL> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users -- Best regards, Teg mailto:t...@djii.com _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
