On Sun, 3 Mar 2013 07:19:11 -0600 "Michael Black" <mdblac...@yahoo.com> wrote:
> One thing I'll point out...the trigger solution is almost linear > performance and constant memory where the single SQL statement will > suffer notably as time goes on in both those measures. Also the > single SQL statement doesn't seem like a good idea if the data is > coming in real time. He never mentioned how big his table is going to > be. If TextField 'A' is deleted, doesn't the entire table have to be updated? Sure, that's O(n), but where n is the size of the table, not the size of the update. Acknowledged, sometimes there are reasons to store derived results. But that choice bears costs, both in updating the database and in engineering it, costs that can be avoided if they can be avoided. Knuth said premature optimization is the root of all evil, and I agree. :-) Normalized data minimize the cost of manipulation. That is why we normalize our databases. As a side-effect, normalized data permit more efficient use of memory, benefiting SELECT, too. --jkl _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
