On 7 Aug 2011, at 10:07pm, P Kishor wrote: > I will let you heavyweights duke it out, but re. the above point, > SQLite (and more databases) have a per row system overhead that can > very quickly overweight the actual data if the data are too granular > with each row storing just a tiny amount. For example, the overhead > for the cells in a raster dataset, if stored one per row, will quickly > surpass the size of the actual data.
You're quite right. If someone was going to write that functionality into a SQLite app in real life they'd probably use 'LIKE' or 'GLOB' and store all the possibilities in one row. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
