4 ms·
A file is still a database, it's often simply a worse one. Go with sqlite instead of generating PHP files for storage.
by treve 10y ago
A file is still a database, it's often simply a worse one. Go with sqlite instead of generating PHP files for storage.
- stephane-klein 10y agoI did that: https://github.com/harobed/gobookmark https://github.com/harobed/gobookmark « Inspired by Shaarli (Delicious clone), easier to install (only one standalone executable). Built with Go - GoBookmark runs without installation on multiple platforms. »
- bigbugbag 10y agohttp://sebsauvage.net/wiki/doku.php?id=php:shaarli#why_not_use_a_real_database_files_are_slow http://sebsauvage.net/wiki/doku.php?id=php:shaarli#why_not_u...
- mastre_ 10y agoGoing with something like sqlite is not always better -- if what it provides is not needed, it's complexity for complexity's sake. PHP arrays are perfectly fine (until you reach a certain size), particularly when using a direct key access scheme. Loading/saving the data is pretty much a file_get_contents|file_put_contents affair, with some inline filters such as serialize & gzip. Couldn't be simpler, and it sounds like it doesn't need to be more complex than that.