Allow Outdated not documented and doesn't seem to work properly about rethinkdb HOT 9 CLOSED

Sigh I remember explicitly making this work. It seems as if the flag is just getting ignored. Will look in to this.

from rethinkdb.

Thanks Joe.

-----Original Message-----
From: Joe Doliner [email protected]
Date: Tue, 13 Nov 2012 11:33:41
To: rethinkdb/[email protected]
Reply-To: rethinkdb/rethinkdb [email protected]
Cc: Daniel [email protected]
Subject: Re: [rethinkdb] Allow Outdated not documented and doesn't seem to
work properly (#51)

Sigh I remember explicitly making this work. It seems as if the flag is just getting ignored. Will look in to this.

Reply to this email directly or view it on GitHub:
#51 (comment)

from rethinkdb.

K, so I just confirmed that this does indeed work with python. So I believe this is a javascript driver problem and nothing else.

from rethinkdb.

FYI. The server is designed to perform out-of-date reads on a per-table basis. That is, if I have a query that contains an inner query, I can have outer reads be performed out-of-date and inner reads by performed normally, or vice versa. It was easier to do on the server, and strictly more powerful.

However, to the user this isn't really useful because typically you'll either run something out-of-date or you won't. For example, you might be doing an analytics query that you'll run out-of-date, or a realtime query that you'll run properly, but you're very unlikely to ever want to mix the two.

So in the clients, we decided to do it as a flag to run. If you call run with the out-of-date flag, the whole thing will be run out of date, otherwise it will be run up to date. You aren't supposed to pass the flag on each table (though some clients may or may not support it, that's purely an accident).

I'll update the api docs for each client, and @wmrowan will check the js implementation soon.

from rethinkdb.

I think the solution we have in python is pretty nice right now. Any table can be explicitly specified as read out dated or not. And a default for all tables can be set in run. People who think of running things in outdated mode will find a flag on run where the expect and people who need something more powerful have it too.

Either way since we've also already released this accident and the drivers all support it (excepting js which doesn't support out dated at all) we should keep it around.

from rethinkdb.

Ah, I see, I forgot that we allow a general flag on a query + specific flags per table. This means it's definitely a js bug.

from rethinkdb.

Fear not the authorities have been alerted.

from rethinkdb.

Reopening, we still need to document this on the API page.

from rethinkdb.

Docs are in rethinkdb-www, just waiting for a push to the webserver.

from rethinkdb.