Wednesday, April 10, 2019, 2:03:24 PM, Peng Yu <pengyu...@gmail.com> wrote:
> Given the much larger disk space required, for an occasional search of > the data, it seems that it makes no sense to use sqlite3 if disk space > is a major concern. Whether it "makes sense" to use SQLite or not, probably only you can decide. If the "zgrep" solution works, and is "fast enough", then there may not be any point in using SQLite. However, possible advantages (depending on your "use cases") include being able to ENFORCE the uniqueness of the string column, and -- depending on the types of query involved -- benefiting from an index which in many cases _should_ speed up the search. And, in response to a couple of your latter emails (where you give _some_ details about your data): you will have a much better chance of people on this list being able to help you if you give a more complete description of the problem: include some sample data from your TSV and the types of searches you want to do. People can then give much more informed help. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
