rethinkdb

I'm trying to remove some portions of data from documents with given fairly simple structure, which will get much deeper and heavier than this as the project goes: { id: "...", name: "...", phone: "...", data: { key1: "val1", ... } ... } I'm aware that there is no way of updating/removing sections from the nested parts other than replacing the whole tree with updated tree. For example, if I want to delete key1 from document data, I need to update the documents data section with a copy of it where key1 is not contained document.update({data: new dict without key1}) Is there any eaiser way of

I am using Rethinkdb 1.10.1 with the official python driver. I have a table of tagged things which are associated to one user: { "id": "PK", "user_id": "USER_PK", "tags": ["list", "of", "strings"], // Other fields... } I want to query by user_id and tag (say, to find all the things by user "tawmas" with tag "tag"). Starting with Rethinkdb 1.10 I can create a multi-index like this: r.table('things').index_create('tags', multi=True).run(conn) My query would then be: res = (r.table('things') .get_all('TAG', index='tags') .filter(r.row['user_id'] == 'USER_PK').run(conn)) However, this query still

Say I have this JSON (sample - a real-life example can be found at apple itunes rss feed ) stored in a RethinkDB table called 'test': { "feed": { "entry": [ { "title": { "label": "Some super duper app" }, "summary": { "label": "Bla bla bla..." } }, { "title": { "label": "Another awsome app" }, "summary": { "label": "Lorem ipsum blabla..." } } ] } } How would I write a ReQL query in JavaScript in order to fetch the summary of all entries ( entry ) which have title containing the string "xyz"? I expect the query result to return an array of matching entry objects, not an array of matching feed .

I'm trying to write the most optimal query to find all of the documents that do not have a specific field. Is there any better way to do this than the examples I have listed below? // Get the ids of all documents missing "location" r.db("mydb").table("mytable").filter({location: null},{default: true}).pluck("id") // Get a count of all documents missing "location" r.db("mydb").table("mytable").filter({location: null},{default: true}).count() Right now, these queries take about 300-400ms on a table with ~40k documents, which seems rather slow. Furthermore, in this specific case, the "location"

I notice that r.table('xxx') not always return a cursor but also sometimes just return docs directly Is the cursor client side implementation only or there are some special things server did to perform queries associate with a cursor ? If it has somethings related to server , what is it and when will I receive a cursor For example I specify result offset and size with skip and limit in the query. Will server return a cursor or just result docs ? A driver returns a cursor when the query returns a stream. Basically when the server produces a stream (a sequence that is lazily computed), the