{"action":"created","issue":{"url":"https://api.github.com/repos/begriffs/postgrest/issues/418","labels_url":"https://api.github.com/repos/begriffs/postgrest/issues/418/labels{/name}","comments_url":"https://api.github.com/repos/begriffs/postgrest/issues/418/comments","events_url":"https://api.github.com/repos/begriffs/postgrest/issues/418/events","html_url":"https://github.com/begriffs/postgrest/issues/418","id":121322908,"number":418,"title":"Moving 1-N and N-N embeds to nested routes.","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-12-09T19:41:43Z","updated_at":"2015-12-13T19:54:15Z","closed_at":null,"body":"Here's an idea I'd like to throw out. In some scenarios it is important to limit/offset the documents returned by 1-N and N-N relations, but we can only limit/offset with headers.\r\n\r\nWhy don't we remove these embedding capabilities and move them to a bested route. This has the advantage of all our current semantics/headers. It also doesn't need single document routes to work. For example:\r\n\r\n`/people/posts?id=eq.5&posts.topic_id=7`"},"comment":{"url":"https://api.github.com/repos/begriffs/postgrest/issues/comments/164293263","html_url":"https://github.com/begriffs/postgrest/issues/418#issuecomment-164293263","issue_url":"https://api.github.com/repos/begriffs/postgrest/issues/418","id":164293263,"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},"created_at":"2015-12-13T19:54:15Z","updated_at":"2015-12-13T19:54:15Z","body":"At the moment, the only warrant is pretty much just that more control/uniform interface is nice 😊\r\n\r\nThere is no real killer issue I see at the moment, but it is a weaker part in the design of PostgREST that could use some discussion and new ideas. I know it's a big part of GraphQL to embed collections, but does that mean it should also be a big part of PostgREST?"}}