4 ms·
As far as I can tell this doesn't support transactions, which imho is table stakes for a persistence solution in 2022.
by im3w1l 4y ago
As far as I can tell this doesn't support transactions, which imho is table stakes for a persistence solution in 2022.
- eesmith 4y agoFWIW, it was added in 1992. https://github.com/python/cpython/commit/dd9ed839d6958f737045306488995a1097df93b8 https://github.com/python/cpython/commit/dd9ed839d6958f73704... with gdbm added in 1994. https://github.com/python/cpython/commit/4b4c664d2e93279c8d749da027000453f9e2cd46 https://github.com/python/cpython/commit/4b4c664d2e93279c8d7... .
- im3w1l 4y agoThe article makes it sound like it's something to consider today (well 2018), that's why I think it's fair to see how well it satisfies modern requirements.
- ok123456 4y agoIf you just need a simple key value store that stays on disk, it's fine.
- jonnycomputer 4y agorequirements for what is the question. "modern requirements" doens't mean that much.
- im3w1l 4y agoWithout transactions the data can become corrupt in case power fails / the process is killed / the container is restarted.
- pjc50 4y agoDBM is the persistence solution of 1979. https://en.wikipedia.org/wiki/DBM_(computing) https://en.wikipedia.org/wiki/DBM_(computing)