Hi Jens et. al., CBL 1.x creates separate tables in the underlying SQLite database to hold the results from the map/reduce functions. Fetching from the database was fast because essentially the results were pre-computed.
With 2.0 it looks like a lot of work is going into the query syntax to be a bit more SQL like. Are the queries transient or do they get materialized into views the first time they're executed and from then on they would run more quickly, just like views? How do we choose what data structures in our documents we want used for index purposes? I have a lot of code written to create CBLViews and to emit the keys and values, so I'm just wondering if I'm in for a big rewrite or not. Thanks, Brendan -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/a7650db6-29db-4b93-b82c-3eda238e1382%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
