I have a situation where I store a data in a text file with tabs, and it's becoming really quite unwieldy to use this.
My workload is quite straightforward, I have a multi-threaded application that logs to this file but from within any single thread at any given time. So from SQLite's perspective only one person will be writing to this database and nobody will ever read from it. The reading happens after the entire database is written to. Is this a use case for SQLite? It seems like the benefit I get from SQLite is that I can do SQL on my previously textual data and optionally add indexes. HOWEVER, this is my catch -- I sometimes have the need to query two databases at the same time. In fact, sometimes I might need to query 100's of these small databases. Would you just recommend querying the 100's in parallel and then joining them in memory or something? Has anybody ever needed to do this? I can only think of querying the database, storing it in memory and then doing things to it. But then I lose the flexibility of SQL. Thoughts? _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
