On Tue, Mar 29, 2011 at 8:39 PM, Diederik van Liere dvanliere@gmail.com wrote:
Basically you are going to develop a sharding solution using sqlite. I think you are overstretching the use case of sqlite (IMHO).
Yes, kindof sharding.
When each revision is on a separate row it will be way easier to run map/reduce jobs else you have to figure out where a revision starts and ends, and each row should contain all variables (IMHO)
Really? Importing from CSV/JSON is easier than running it from sqlite?
Note that I'm not really 'fixated' on sqlite - if the community feels that JSON (I don't think CSV is very suitable for full fledged dumps) would be good, I'll be glad to work on that....