z29LiTp5qUC30n
Joined 9 years ago
Joined 9 years ago
Every time something is updated or deleted, the entire previous record is inserted into its corresponding _A table with who did it and when (and optionally for what transaction number)
so delete from foo results in an insert into foo_A before the delete occurs. so update to bar results in an insert into bar_A before the update occurs and rolling back a delete results in picking the old values out of the _A table and rolling back an update results in picking the old values out of the _A table and inserting the current values into the _A table before the updating the main table.
It is that lack of information, which prevents hardware drivers from entering the Linux Kernel main tree; which along with Tivoization are the leading drivers of e-waste and unsecured systems.
Try you only have a single bootloader and a little bit of source code and building all the way up to a complete linux distro
https://github.com/fosslinux/live-bootstrap
(checkout the builder-hex0/fiwix work)
Just wish I could have typed half as well as Hugh Jackman in Swordfish; then I wouldn't feel so sorry for all of the bugs I introduced into production because of her.
Not to mention the absolutely bad design for handling merge conflicts (punt to human if more than 1 person touched a file seriously???)
Heck the cryptocurrency community has repeatedly sent death threats to the very people working on their root of trust.
People just plain suck
https://github.com/oriansj/stage0/blob/master/High_level_pro...
It'll dehex any non-humanly used ASCII characters