3 ms·
> By this I mean, if you need a database at all, you should jump to having a relational one straight away, and default to a relational schema, even if your earl
by Jtsummers 5y ago
> By this I mean, if you need a database at all, you should jump to having a relational one straight away, and default to a relational schema, even if your earliest set of requirements could be served by a “document database” or some basic flat-file system.
Emphasis added.
So the author probably agrees with you that a calculator doesn’t need a database.
- tonyarkles 5y agoI’m laughing a bit at the calculator example though because, in 2021, if the calculator started to be configurable from within the UI out have any kind of persistence (eg keeping your calculation history from session to session) my very first inclination would be to grab SQLite and skip right past plain text/YAML/.ini etc files.
- goto11 5y agoThe calculator on Windows does persist a few settings, for example windows size and whether "scientific" or "standard" mode is selected. This could be saved in a config file or some other storage format. Windows has a simple per-application key-value store for such settings. A relational database would be overkill and increase overall complexity.