Make primary key default happen on the server for eqJoin, between, and get about rethinkdb HOT 6 CLOSED

Moving to backlog until more pressing issues are worked out.

from rethinkdb.

This query fails:

r.db('w').table('design').eqJoin('id', r.db('w').table('user'), 'id_user').zip().run()

The primary key of the table design is "id" and the one of the table user is "id_user".

I get this error:

Runtime Error: Attribute: id is not the primary key (id_user) and thus cannot be selected upon.
    r.db('w').table('design').concatMap(function(arg0_10) {return r.let({'right':r.db('w').table('user').get(r.letVar('arg0_10')('id'), 'id')}, r.branch(r.letVar('right').ne(r.expr(null)), r.expr([r.expr({'left':r.letVar('arg0_10'), 'right':r.letVar('right')})]), r.expr([])))}).map(function(arg0_11) {return r.branch(r.letVar('arg0_11').contains(right), r.letVar('arg0_11')('left').merge(r.letVar('arg0_11')('right')), r.letVar('arg0_11')('left'))})

So the problem is not just that the default key is "id" but that the default key is always "id" even if the user define the primary key.

from rethinkdb.

That seems to be a bug in the driver. @wmrowan -- could you take a look?

EDIT: this is a separate issue from the original one, so @wmrowan -- perhaps you should open a new one that we fix now.

from rethinkdb.

In regards to the original issue described here, I'd be in favor of merging this into the protocol refactoring process since this is an already acknowledged goal of that effort. In the future, these optional attributes will be included as optargs on their respective operations in the protocol spec and the server will use the known primary key for the table if the optarg is not provided. Given this, I see little reason to fix this now.

from rethinkdb.

Meant to close the other one

from rethinkdb.

This is no longer relevant, closing.

from rethinkdb.