Hi Eric, On 24/4/2012 10:03 PM, Eric Minbiole wrote:
Similar to Pavel's suggestion, our implementation maintains a simple cache of prepared statements, keyed by the SQL query that created them. For example:pStatement = Cache.GetQuery("SELECT * FROM xyz"); would return the cached statement if the query had been seen before, or would auto-create it, if needed. This (attempts to) give the best of both worlds: Statements are only created / prepared once, improving run-time performance. In addition, the programmers aren't burdened with trying to figure out up-front which queries might / might not be used later, simplifying development. This approach has worked well in our application.
Thanks! This is similar to what we were thinking... it's good to know that you're successfully using it.
Best Regards, Mohit. 25/4/2012 | 12:01 AM. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
