3 ms·

Your database starts to look like git... Think about a jet engine. Let's say you figure out that a part is defective and will cause a failure. You want to iden

Your database starts to look like git... Think about a jet engine. Let's say you figure out that a part is defective and will cause a failure. You want to identify every plane that has one of those parts in it. What if you find that some of them had a bad oil pump that shortened the life of some bearings. You want to know every engine that had one of those pumps, so you can replace other parts. I dont know if they do this with jets but there are quite a few places that take thee concept much further than this.

smaudet 2y ago
> Your database starts to look like git... No, your table archives start to look like git. Which is not a bad thing, version control on data in a database is very difficult, if not impractical to realize, I would take any history that I can get... "Synthetic" keys are just that, keys for tables that only have meaning within the context of that data. You can of course relate your records to as many other tables as you wish, but you identify records via those keys, nothing more.