3 ms·
I'm always reluctant about going completely schemaless. Reminds me of the blog post by FriendFeed about how they use MySQL, highly recommended: http://bret.apps
by shazow 16y ago
I'm always reluctant about going completely schemaless. Reminds me of the blog post by FriendFeed about how they use MySQL, highly recommended: http://bret.appspot.com/entry/how-friendfeed-uses-mysql http://bret.appspot.com/entry/how-friendfeed-uses-mysql
I feel like like there needs to be a better middleground for having some schema but being able to augment it easily with metadata that you're not querying against (yet). Then later extracting the metadata into queryable columns.
I wrote a post outlining some ideas of how to do this: https://github.com/shazow/everything/blob/master/idea/arbitrarily-structured-data-in-rdbms.md https://github.com/shazow/everything/blob/master/idea/arbitr...
I've only implemented bits and pieces of this in practice, huge convenience so far.
- joshu 16y agoI think this is exactly right. Have a document store and a (separate?) index store.
- iamclovin 16y agoJames Golick implemented this idea in Ruby last year: https://github.com/jamesgolick/friendly https://github.com/jamesgolick/friendly We used Friendly at my previous company wego.com and t worked quite well although I don't know shehar they at still using it. (Friendly doesnt look like it's in activ development)