Twitter | Pretraživanje | |
Reid D. M. 1. velj
Databases fucking suck send tweet
Reply Retweet Označi sa "sviđa mi se"
Reid D. M. 1. velj
Odgovor korisniku/ci @arrdem
"put the thing in a database" great now it has no version history, lives on a server somewhere which could fail, and requires special tools to access.
Reply Retweet Označi sa "sviđa mi se"
Reid D. M. 1. velj
Odgovor korisniku/ci @arrdem
anyway text data formats are fine, and you can make them better.
Reply Retweet Označi sa "sviđa mi se"
Chadwick Blazington 1. velj
Odgovor korisniku/ci @arrdem
filesystems suck complete ass, though, even more-so than most databases.
Reply Retweet Označi sa "sviđa mi se"
Reid D. M. 1. velj
Odgovor korisniku/ci @stdlib
yes, but consider single files
Reply Retweet Označi sa "sviđa mi se"
Chadwick Blazington 1. velj
Odgovor korisniku/ci @arrdem
i don't think that's much better, because you're almost always stuck with POSIX as a common denominator anyway (which sucks) so you're still at the mercy of the fs layer. e.g. how to safely rename files with fsync is unspecified.
Reply Retweet Označi sa "sviđa mi se"
Chadwick Blazington 1. velj
Odgovor korisniku/ci @arrdem
by then you might as well say fuck it and upgrade your filesystem and interface with it directly through non-standard means. you'll immediately want transactions for safety, but now you're just using "flat" namespaces as your tables. it *is* a database at that point
Reply Retweet Označi sa "sviđa mi se"
Chadwick Blazington
VMS basically got this right IIRC; rather than thinking of files as blobs, it treated them as objects that were just tables. a text file was "just" a set of rows that a text editor contiguously visualized, like Excel. two people could trivially read/edit files concurrently, etc
Reply Retweet Označi sa "sviđa mi se" More