On Nov 5, 2009, at 5:43 PM, Kavita Raghunathan wrote: > > I saw a presentation on sqlite by Dr Hipp that mentioned that > anytime I'm > storing data in structures or tables, I should be thinking about using > sqlite instead. > > Would it be more efficient to use the sqlite database to store a > table that > Looks like this: where lets say I'm looking for the word "auto- > align". Would > the query be quicker than searching through this table in a "for" or > while > loop? Assume the table has about 200 entries. I want to know if the > performance will be better and if I should consider storing these > constants > in the database.
Raw C code will be faster. But is speed really the criteria here? What about correctness? Or ease of maintenance and enhancement? How fast does your program really need to go? If it is absolutely critical that you find your answer in nanoseconds, then by all means use C code. But if you are operating on human timescales (tens or hundreds of milliseconds) then SQLite will be fast enough and, depending on what you are trying to accomplish, might be less error prone and easier to expand and enhance down the road. D. Richard Hipp [email protected] _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
