{"action":"created","issue":{"url":"https://api.github.com/repos/meteor/postgres-packages/issues/24","labels_url":"https://api.github.com/repos/meteor/postgres-packages/issues/24/labels{/name}","comments_url":"https://api.github.com/repos/meteor/postgres-packages/issues/24/comments","events_url":"https://api.github.com/repos/meteor/postgres-packages/issues/24/events","html_url":"https://github.com/meteor/postgres-packages/issues/24","id":107928323,"number":24,"title":"schema in PG.Table option object","user":{"login":"robfallows","id":6086035,"avatar_url":"https://avatars.githubusercontent.com/u/6086035?v=3","gravatar_id":"","url":"https://api.github.com/users/robfallows","html_url":"https://github.com/robfallows","followers_url":"https://api.github.com/users/robfallows/followers","following_url":"https://api.github.com/users/robfallows/following{/other_user}","gists_url":"https://api.github.com/users/robfallows/gists{/gist_id}","starred_url":"https://api.github.com/users/robfallows/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/robfallows/subscriptions","organizations_url":"https://api.github.com/users/robfallows/orgs","repos_url":"https://api.github.com/users/robfallows/repos","events_url":"https://api.github.com/users/robfallows/events{/privacy}","received_events_url":"https://api.github.com/users/robfallows/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-09-23T14:09:57Z","updated_at":"2015-09-24T01:33:55Z","closed_at":null,"body":"I'm thinking it would be cool to start building out the options object by adding a `schema` object. This could (on the server) create the table if it doesn't exist and validate it if it does. We could move closer to the simplicity of the `Mongo.Collection` with this functionality and reduce the need for migrations to set stuff up.\r\n\r\nI've been spitballing a few ideas and I think it would be easy to create the table (less easy to validate, but still doable)."},"comment":{"url":"https://api.github.com/repos/meteor/postgres-packages/issues/comments/142778666","html_url":"https://github.com/meteor/postgres-packages/issues/24#issuecomment-142778666","issue_url":"https://api.github.com/repos/meteor/postgres-packages/issues/24","id":142778666,"user":{"login":"stubailo","id":448783,"avatar_url":"https://avatars.githubusercontent.com/u/448783?v=3","gravatar_id":"","url":"https://api.github.com/users/stubailo","html_url":"https://github.com/stubailo","followers_url":"https://api.github.com/users/stubailo/followers","following_url":"https://api.github.com/users/stubailo/following{/other_user}","gists_url":"https://api.github.com/users/stubailo/gists{/gist_id}","starred_url":"https://api.github.com/users/stubailo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/stubailo/subscriptions","organizations_url":"https://api.github.com/users/stubailo/orgs","repos_url":"https://api.github.com/users/stubailo/repos","events_url":"https://api.github.com/users/stubailo/events{/privacy}","received_events_url":"https://api.github.com/users/stubailo/received_events","type":"User","site_admin":false},"created_at":"2015-09-24T01:33:55Z","updated_at":"2015-09-24T01:33:55Z","body":"Yeah we actually had this at first and then removed it because it turns out that having migrations be separate is a good idea. But it could be cool to verify that the scheme matches and remind the developer to run migrations!"}}