On 13 Feb 2011, at 5:53pm, Jim Wilcoxson wrote: > I also found this page, used to force a Linux system crash: > > http://evuraan.blogspot.com/2005/06/how-to-force-paniccrash-in-linux.html > > I seem to remember a post that SQLite commit/sync is tested with the kill > command, but it seems like actually crashing the machine (which is done > without a sync first) might be a better test.
You can do extensive experimentation an find out exactly how one setup acts. One particular hard disk, motherboard, operating system, and (disk) device driver. But change any variable, even upgrade to a later version of the OS or device driver, and you can get different behaviour. Same thing if you move the jumpers on the hard disk or upgrade its firmware. So if you test your programming on your own computer but send your application to customers you don't know how it'll perform. At the level you're worrying about, you're learning too much about a very narrow subject. If you need a general solution you have to write for the specs, not one particular setup. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
