diff options
Diffstat (limited to '')
| -rw-r--r-- | _posts/2020-08-31-the-database-i-wish-i-had.md | 10 |
1 files changed, 9 insertions, 1 deletions
diff --git a/_posts/2020-08-31-the-database-i-wish-i-had.md b/_posts/2020-08-31-the-database-i-wish-i-had.md index 7bb0036..3ffbb6c 100644 --- a/_posts/2020-08-31-the-database-i-wish-i-had.md +++ b/_posts/2020-08-31-the-database-i-wish-i-had.md @@ -179,7 +179,7 @@ application specific conflict resolution functions, like: Some databases try to make this "easy", by choosing a strategy for you, but I've found that different applications require different conflict resolution strategies. Instead, the database should leave this up to the user to decide, -and provide tool for them to do it. +and provide tools for them to do it. [**Three-way merges in version control**][3-way-merge] are the best example, performing automatic merges when possible and asking the user to resolve @@ -243,3 +243,11 @@ between POSIX and IndexedDB will probably be the biggest challenge. I got myself a few books on databases to start. I wonder if I'll ever be able to get this done. + +## External links + +See discussions on [Reddit][reddit], [lobsters][lobsters] and [HN][hn]. + +[reddit]: https://www.reddit.com/r/programming/comments/ijwz5b/the_database_i_wish_i_had/ +[lobsters]: https://lobste.rs/s/m9vkg4/database_i_wish_i_had +[hn]: https://news.ycombinator.com/item?id=24337244 |