On 02/25/2015 10:31 AM, Rob Richardson wrote: > A Google search for "USS Yorktown" turned up the following: > > "On September 21, 1997, a division by zero error on board the USS Yorktown > (CG-48) Remote Data Base Manager brought down all the machines on the > network, causing the ship's propulsion system to fail." > > RobR > > -----Original Message----- > <snip> > > To eliminate the need to reference a table would require combining 300 > tables into one table. A user editing entries for one space could crash the > whole system. That's basically what happened aboard the Yorktown in 1997. A > cook trying to enter an item into the lunch menu killed the engines on the > ship. > > <more snip> > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > That's the basic story. The DB people claimed the OS should have protected against the division by zero, the OS people claimed the DB should have not let the cook overflow the menu record and cause a division by 0. The ship had to be towed in, the ship got under weigh in a couple of hours, etc. My goal is to make sure that nothing like any of that happens. Or if it does has the least effect possible.
It's beginning to look like I should replace the arduinos with R-Pi model A running sqlite3. The 'a' db then becomes a data collection and report generator, each remote has an individual 'b' db. Everything can be managed by simple sql and Python scripts. The R-Pi has more computing power than the old towers and are lots cheaper. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: <http://mailinglists.sqlite.org/cgi-bin/mailman/private/sqlite-users/attachments/20150225/f727abfc/attachment.pgp>
