Add defaults to getattr, and defaults command on streams about rethinkdb HOT 11 CLOSED

@sojin this is because some of the documents don't have age as an attribute and rethink is strict about errors (if an attribute is missing and you try to use it, it'll throw an error). We'll make an api much nicer to deal with cases like this, but in the meantime you can try this:

db('python_tutorial').table('heroes').filter(lambda row: row.contains('age') & (r['age'] ==26)).run()

from rethinkdb.

Thanks, that did the trick.We are evaluating Rethink as an alternative for MongoDB, still trying to get my head around the docs. :)

from rethinkdb.

Great, all questions are welcome (irc, here, or google groups)!

from rethinkdb.

Ok, we need to add the following two enhacements:

# Defaults in attr access
table('foo').filter(r['bar', 0] == 1).run()

# Defaults command on streams
table('foo').defaults({ 'bar': 0 }).filter(r['bar'] == 1).run()

Moving to backlog, will address when some pressing initial issues are worked out.

from rethinkdb.

Can we have something to also have every attribute to default to nil? (I don't want to spend my time specifying the name of each attribute I'm going to use in the filter)

from rethinkdb.

I reopened #183, so we may try to find a different approach to this problem (although adding a modifier to evaluate missing attributes to nil is one option).

from rethinkdb.

I think a default command would be a good thing, though it shouldn't be used to address #183. I think there should be a ni | undefined value that behaves a lot like NaN and causes the row to be removed by default.

from rethinkdb.

The discussion if this has become a bit fractures but I think that were all
in agreement (although we haven't explicitly said it) that filter and
similar commands will be looking for Nothing and dropping those rows.
On Feb 23, 2013 6:27 PM, "Craig" [email protected] wrote:

I think a default command would be a good thing, though it shouldn't be
used to address #183 #183.
I think there should be a ni | undefined value that behaves a lot
like NaN and causes the row to be removed by default.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/27#issuecomment-14002217.

from rethinkdb.

This may or may not be a dup of #183, depending on how we look at it. I'll consider this shortly.

from rethinkdb.

FYI -- defaults on streams could be implemented as a special kind of merge, which would require a new merge function to do right, which would require a map over objects to do right (of course we could also just do it, and fill in the architectural foundation later). Anyway, this is all discussed on google groups, and the link to the discussion is in the body of the issue #186. (Just so we don't lose track of the fact that these things are related).

from rethinkdb.

This issue has now been subsumed by #570. Closing.

from rethinkdb.