{"comment":{"url":"https://api.github.com/repos/numtel/pg-live-select/comments/12845517","html_url":"https://github.com/numtel/pg-live-select/commit/aec510582e5ed832d51b2e9369de398ae8fc78ea#commitcomment-12845517","id":12845517,"user":{"login":"numtel","id":518698,"avatar_url":"https://avatars.githubusercontent.com/u/518698?v=3","gravatar_id":"","url":"https://api.github.com/users/numtel","html_url":"https://github.com/numtel","followers_url":"https://api.github.com/users/numtel/followers","following_url":"https://api.github.com/users/numtel/following{/other_user}","gists_url":"https://api.github.com/users/numtel/gists{/gist_id}","starred_url":"https://api.github.com/users/numtel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/numtel/subscriptions","organizations_url":"https://api.github.com/users/numtel/orgs","repos_url":"https://api.github.com/users/numtel/repos","events_url":"https://api.github.com/users/numtel/events{/privacy}","received_events_url":"https://api.github.com/users/numtel/received_events","type":"User","site_admin":false},"position":301,"line":301,"path":"index.js","commit_id":"aec510582e5ed832d51b2e9369de398ae8fc78ea","created_at":"2015-08-23T05:32:55Z","updated_at":"2015-08-23T05:32:55Z","body":"Having that limitation of unique rows was discussed during initial development. I had always thought it an unnecessary restriction but it does offer a space for many optimizations.\r\n\r\nI can't think of any query I've used in a site or app that wouldn't have unique rows, (they always seem to have an `id` column included) but the possibility is definitely there.\r\n\r\nIn order to move to a system that syncs rows and would allow for client-side SQL, it has always been clear that primary keys would be required on all tables. \r\n\r\nMaybe it is a good idea to impose this restriction. "}}