On 3 Aug 2010, at 10:20pm, jeff archer wrote: > Generally, in the past I have always used normalized data but thought I read > this might not always be most efficient in SQLite. Is there any "rule of > thumb"?
Generally speaking, don't worry about it. Do whatever makes your programming simplest and easiest. Worry about efficiency only if the results run too slowly or take too much filespace. It's unlikely that any change you can reasonably make will make much difference to your results. About all the other things you mentioned: I don't see anything that strikes me as wrong, but I'm not an expert on every aspect of operation. The one thing you will notice is that, because SQLite does not cache indexing information between calls, creating the best index for each SELECT command has a huge difference on how fast the SELECT runs. This is not quite as important for MS SQL Server. So if the speed of your SELECTs matters to you design your indexes with care. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
