3 ms·

Alternately: file formats and saving to disk are just a very primitive database where the cache is the size of the entire database (you load the entire thing in

Alternately: file formats and saving to disk are just a very primitive database where the cache is the size of the entire database (you load the entire thing into memory). Also you don't have good disaster recovery (see "I forgot to save and lost the last half hour of work!"). Also, auto-save is a very primitive form of a write ahead log

paulddraper 3y ago
And databases are files :) --- The essential distinction is the granularity of reads/writes
- paulryanrogers 3y ago
  Usually but not necessarily. Some can access raw disk blocks without a traditional file system.
  - doubled112 3y ago
    Won't Oracle do that for a performance increase?
    - paulddraper 3y ago
      Oracle claims a 5-10% perf increase (on Windows) [1] [1] https://docs.oracle.com/en/database/oracle/oracle-database/12.2/ntqrf/raw-partition-overview.html https://docs.oracle.com/en/database/oracle/oracle-database/1...
spullara 3y ago
as long as auto-save doesn't overwrite the file directly and can corrupt it by failing in the middle!
unmole 3y ago
Q: What's the difference between filesystems and databases? A: Marketing.
- rocqua 3y ago
  A: indexing, schema flexibility, performance
  - gdprrrr 3y ago
    /var/lib/mlocate.db ;)
- hobs 3y ago
  The amount of work the second one puts into not letting me fuck up my own work unless I do it on purpose.
jahewson 3y ago
It’s true! The old MS Office binary formats were built on top of FAT.