I agree. I would add that the same considerations apply to denormalizing a database to gain efficiency. Start with a normalized database. If performance is lacking, try various kinds of denormalization. Back out any denormalization that doesn't improve performance.
When testing performance, be sure to test all use cases. Denormalization tends to speed up SELECTs at the expense of slowing down INSERTs, UPDATEs, and DELETEs. - Richard Klein [EMAIL PROTECTED] wrote: > "Lee Crain" <[EMAIL PROTECTED]> wrote: >> I am debating the performance gains to be realized, if any, by indexing a >> particular table in a system implementation for which I am responsible. >> > > You are getting way ahead of yourself. > > Stop trying to speculate about whether or not an index > or indices will be useful. Write your application first. > Then test it. Measure the speed. Then add an index and > test and measure again. Compare the measurements. Add > a different index or combination indices. Repeat until > done. > > Premature optimization leads to bad design. Build your > application first, then measure it to see where optimization > is needed. > > -- > D. Richard Hipp <[EMAIL PROTECTED]> > > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
