5 ms·
He means a flat file of JSON records. Your sarcasm is unnecessary and uncharitable.
by jemfinch 15y ago
He means a flat file of JSON records. Your sarcasm is unnecessary and uncharitable.
- deleted 15y ago[deleted]
- stfp 15y agoAND fun
- sausagefeet 15y agoHow do you know he means that?
- jemfinch 15y agoBecause it's the only interpretation that makes sense, and charitable discussion demands that I assume my interlocutors are reasonable people who say things that make sense until I have evidence to the contrary.
- statictype 15y agoThe sarcasm was perhaps a little mean but he has a point. If a flat text file storing JSON could replace your database, then you probably never needed a DB in the first place.
- daleharvey 15y agoLots of people use full blown rdbms's when they dont need to (see blogs), its not a silly point and the sarcasm was unwarranted
- alextingle 15y agoSarcasm is never unwarranted.
- code_duck 15y agoIf you can use SQLlite, you probably didn't need a real database. So the use cases overlap a bit with flat-files and JSON.
- mmaunder 15y agoThe JSON flat file sounds like variable length records where length is determined by parsing each record with global reader/writer locking? It's like public storage where you have to sift through everyone else's crap to get to yours, every item is stored in a bulk cargo box and only one customer gets to store their stuff at a time. If you're interested in db internals, here's a few algorithms that MySQL uses. Note this doesn't cover InnoDB which performs far better under high concurrency loads and offers row level locking, clustered indexes, an excellent caching algorithm, foreign key constraints with cascade, etc..etc... http://forge.mysql.com/wiki/MySQL_Internals_Algorithms http://forge.mysql.com/wiki/MySQL_Internals_Algorithms
- code_duck 15y agoThe way I've stored things in flat files is to make use of the file system's lookup capabilities. I wouldn't suggest storing data that may be requested or written to by more than one client at once with a method such as this, either. I wouldn't try to use it like a C array or anything. One file per user or more makes sense. I've also used stuff like this for system admin scripts. Something like user_id=int(request.GET['id']) data_type=int(request.GET['id']) json_file="{0}-{1}-chart_data.json".format(user_id,data_type) #get the file, decode, etc. It's a quick and dirty caching method that has good persistence, of course, is relatively performant under low loads and easy to understand. Thanks, I'll check out the MySQL thing, but I'm not actually intending to build my own database.
- zem 15y agowhat's your cutoff line for something to be a "real database"? sqlite is fully acid compliant.
- code_duck 15y ago