4 ms·
Sometimes, when I want to play with/benchmark a new technology stack, framework, library, etc, I run into the problem of not having a database to test out with
by retroafroman 15y ago
Sometimes, when I want to play with/benchmark a new technology stack, framework, library, etc, I run into the problem of not having a database to test out with it. As a result, I spend a non-trivial amount of time (I'm not the best coder) banging out a script that fills out a custom database with the fields and datatypes I want. However, this strikes me as an example of unnecessary 'yak shaving'. My first impulse is to make a web app that creates custom databases, but luckily I googled around a bit and found this first which already does that: http://www.generatedata.com/#generator http://www.generatedata.com/#generator
- rgarcia 15y agoExcept generatedata has a 200 record limit. Luckily it's open source, so if you can host a PHP app you can bump it up to whatever you like. I did this a few weeks ago (bumped the limit up to 10000): https://github.com/rgarcia/generatedata https://github.com/rgarcia/generatedata http://smooth-frost-5744.herokuapp.com/ http://smooth-frost-5744.herokuapp.com/
- zerop 15y agoLarge Datasets open to public : http://www.quora.com/Data/Where-can-I-get-large-datasets-open-to-the-public http://www.quora.com/Data/Where-can-I-get-large-datasets-ope...
- darkxanthos 15y agoWhy even use a database then? Fill your memory with a bunch of objects until you need persistence... Even then a flat file works well until you expect multiple people to post at once.