{"action":"created","issue":{"url":"https://api.github.com/repos/begriffs/postgrest/issues/354","labels_url":"https://api.github.com/repos/begriffs/postgrest/issues/354/labels{/name}","comments_url":"https://api.github.com/repos/begriffs/postgrest/issues/354/comments","events_url":"https://api.github.com/repos/begriffs/postgrest/issues/354/events","html_url":"https://github.com/begriffs/postgrest/issues/354","id":116417488,"number":354,"title":"Reducing ambiguity in query parameters","user":{"login":"calebmer","id":8282507,"avatar_url":"https://avatars.githubusercontent.com/u/8282507?v=3","gravatar_id":"","url":"https://api.github.com/users/calebmer","html_url":"https://github.com/calebmer","followers_url":"https://api.github.com/users/calebmer/followers","following_url":"https://api.github.com/users/calebmer/following{/other_user}","gists_url":"https://api.github.com/users/calebmer/gists{/gist_id}","starred_url":"https://api.github.com/users/calebmer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/calebmer/subscriptions","organizations_url":"https://api.github.com/users/calebmer/orgs","repos_url":"https://api.github.com/users/calebmer/repos","events_url":"https://api.github.com/users/calebmer/events{/privacy}","received_events_url":"https://api.github.com/users/calebmer/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-11-11T20:45:18Z","updated_at":"2015-11-12T22:59:30Z","closed_at":null,"body":"Say I have a post object which looks like this:\r\n\r\n```json\r\n{\r\n  \"id\": 5,\r\n  \"headline\": \"Hello, world!\",\r\n  \"author\": 2,\r\n  \"editor\": 7\r\n}\r\n```\r\n\r\nWhere both `author` and `editor ` link to a row in the `person` table.\r\n\r\nThe current `select` parameter does not allow us to expand both (one would try something like: `?select=person(*)`). How should we resolve this issue?\r\n\r\nI propose we allow for the following: `?select=author(*),editor(*)` and that expands the `author` and `editor` fields respectively. Thus above would become:\r\n\r\n```json\r\n{\r\n  \"id\": 5,\r\n  \"headline\": \"Hello, world!\",\r\n  \"author\": {\r\n    \"id\": 2,\r\n    \"name\": \"Jen\"\r\n  },\r\n  \"editor\": {\r\n    \"id\": 7,\r\n    \"name\": \"Sam\"\r\n  }\r\n}\r\n```\r\n\r\nOne scary part of this, however, is that in one request `author` and `editor` return a number, and in the other `author` and `editor` return objects (personally, I don't see this as too big an issue, but it must be considered nonetheless). One solution to this problem is using JSON-LD (#343) where `author` and `editor` always return an object with an `@id` field."},"comment":{"url":"https://api.github.com/repos/begriffs/postgrest/issues/comments/156263952","html_url":"https://github.com/begriffs/postgrest/issues/354#issuecomment-156263952","issue_url":"https://api.github.com/repos/begriffs/postgrest/issues/354","id":156263952,"user":{"login":"diogob","id":20662,"avatar_url":"https://avatars.githubusercontent.com/u/20662?v=3","gravatar_id":"","url":"https://api.github.com/users/diogob","html_url":"https://github.com/diogob","followers_url":"https://api.github.com/users/diogob/followers","following_url":"https://api.github.com/users/diogob/following{/other_user}","gists_url":"https://api.github.com/users/diogob/gists{/gist_id}","starred_url":"https://api.github.com/users/diogob/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/diogob/subscriptions","organizations_url":"https://api.github.com/users/diogob/orgs","repos_url":"https://api.github.com/users/diogob/repos","events_url":"https://api.github.com/users/diogob/events{/privacy}","received_events_url":"https://api.github.com/users/diogob/received_events","type":"User","site_admin":false},"created_at":"2015-11-12T22:59:30Z","updated_at":"2015-11-12T22:59:30Z","body":"Just please, let's keep away from nested routes :D"}}