One way to to do an inner join in RethinkDB with the eqJoin function:<\/p>\n
r.db('test')\n .table('user_actions')\n .filter({file_name: 'test2.pdf'})\n .eqJoin('user_id', r.table('users'))\n<\/pre>\nThe biggest disadvantage to this API is that you can’t easily reverse the order of the tables. In this case, I’m taking users and adding audit information to them, and in SQL I would be inclined to reverse the order of the join. While this is functionally identical, you may find cases where this forces you to think differently about the process.<\/p>\n
{\n \"left\": {\n \"action\": \"open file\" ,\n \"file_name\": \"test2.pdf\" ,\n \"id\": \"07123881-5d95-4596-b0b4-3b1f50860bfe\" ,\n \"user_id\": \"450e77d6-d5c6-4533-b2d7-c0158bb097c9\"\n } ,\n \"right\": {\n \"first_name\": \"test\" ,\n \"id\": \"450e77d6-d5c6-4533-b2d7-c0158bb097c9\" ,\n \"work_history\": [\n {\n \"role\": \"role 1\"\n },\n {\n \"role\": \"role 2\"\n }\n ]\n }\n}<\/pre>\nNote that the above result makes objects called “left” and “right” in the result, which is not typically what you’d want – you can fix this by adding .zip:<\/p>\n
\nr.db('test')\n .table('user_actions')\n .filter({file_name: 'test2.pdf'})\n .eqJoin('user_id', r.table('users'))\n .zip()\n<\/pre>\nThe other way to do this is with “innerJoin” which requires more effort, but is more flexible and lets you write things that are exact equivalences to SQL:<\/p>\n
\nr.db('test')\n .table('user_actions')\n .filter({file_name: 'test2.pdf'})\n .innerJoin(r.table('users'),\n (action, user) => \n action('user_id').eq(user('id')))\n<\/pre>\nAnd this is the final output:<\/p>\n
\n{\n \"action\": \"open file\" ,\n \"file_name\": \"test2.pdf\" ,\n \"first_name\": \"test\" ,\n \"id\": \"450e77d6-d5c6-4533-b2d7-c0158bb097c9\" ,\n \"user_id\": \"450e77d6-d5c6-4533-b2d7-c0158bb097c9\" ,\n \"work_history\": [\n {\n \"role\": \"role 1\"\n } ,\n {\n \"role\": \"role 2\"\n }\n ]\n}\n<\/pre>\n","protected":false},"excerpt":{"rendered":"One way to to do an inner join in RethinkDB with the eqJoin function: r.db(‘test’) .table(‘user_actions’) .filter({file_name: ‘test2.pdf’}) .eqJoin(‘user_id’, r.table(‘users’)) The biggest disadvantage to this API is that you can’t easily reverse the order of the tables. In this case, I’m taking users and adding audit information to them, and in SQL I would be … <\/p>\n