Simon Slavin wrote: > On 1 Jun 2010, at 11:59pm, Scott Hess wrote: >> Well, really, what you want is "SQLite, for this table, I want to these >> SELECT and UPDATE statements in this ratio, what indices would be ideal?" > > That's often handled with smart caching. The cache system notes down how > often each item is hit, and uses that information to decide which items > should be wiped from the cache when more memory is needed. (That's a massive > simplification.). Some of the proposed replacements for SQL involve smart > systems like this: the programmer never creates any indices at all. It's up > to the database engine to decide how to do the searches most efficiently, the > programmer just says how much memory it can use to do so.
What are some examples of the proposed SQL replacements that do this? -- Darren Duncan _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
