On Tue, Aug 30, 2011 at 3:40 PM, Davorin Rusevljan < [email protected]> wrote:
> On Tue, Aug 30, 2011 at 4:27 PM, Mariano Martinez Peck > <[email protected]> wrote: > > I don't understand. What is the difference from the querying and indexing > > point of view between serializing with JSON or a binary serializer. > > let's say you have a class: > > Object subclass: #MyClass > instanceVariableNames: 'a b' > classVariableNames: '' > poolDictionaries: '' > category: 'Example' > > and you serialize it into the json to something like > > { > '_id': 'lkjjfdjdjdj', > 'a': 'value of a', > 'b': 'value of b' > } > > than you can ask CouchDB to fetch you all object where for instance a is > 'Aha!' > > while if you serialize it as: > > { > '_id': 'lkjjfdjdjdj', > 'fuel_blob': 'AAXsdfkljijS3SM .....' > } > > CouchDB has no idea how to look into the a, and select appropriate objects. > > Interesting. Now I understand. So I guess the same happens with all the rest of NoSQL databases? I am right no assume that if I want to be able to do queries without bringing the whole graph into memory, I need to store the data in JSON ? thanks! -- Mariano http://marianopeck.wordpress.com
