Lars Wirzenius on Nostr: When designing a database schema and related application functionality of managing ...
When designing a database schema and related application functionality of managing data, think really carefully about what data stored in the database may need to be changed. If in doubt, allow it to be changed. If nothing else, mistakes in data entry can be devastating. Things that I've seen that needed to be changed: a person's name, birth date, gender, physical characteristics, biometrics, SSN; a company's name, registration number.
Even UUID picked when inserting a row.
Published at
2025-01-21 15:17:32Event JSON
{
"id": "5e3ed336701588785b862d576ee3b3aac8f674f02d6ec36369e56a926f613e31",
"pubkey": "b10dc1f389e232d431638f9ab5e479818b1bfab197d62e420c170baf0bec09cb",
"created_at": 1737472652,
"kind": 1,
"tags": [
[
"content-warning",
"rant; database"
],
[
"proxy",
"https://toot.liw.fi/users/liw/statuses/113867007737684361",
"activitypub"
]
],
"content": "When designing a database schema and related application functionality of managing data, think really carefully about what data stored in the database may need to be changed. If in doubt, allow it to be changed. If nothing else, mistakes in data entry can be devastating. Things that I've seen that needed to be changed: a person's name, birth date, gender, physical characteristics, biometrics, SSN; a company's name, registration number.\n\nEven UUID picked when inserting a row.",
"sig": "f48af79990f2a2a31ed35e4367a01798bffe9c581abcd3e2e2c667d303e3187ebf4698fa7551df1c706771f791239f415b5a855c29c98339fb6f6dece1c2d66d"
}
