{"action":"created","issue":{"url":"https://api.github.com/repos/sequelize/umzug/issues/94","repository_url":"https://api.github.com/repos/sequelize/umzug","labels_url":"https://api.github.com/repos/sequelize/umzug/issues/94/labels{/name}","comments_url":"https://api.github.com/repos/sequelize/umzug/issues/94/comments","events_url":"https://api.github.com/repos/sequelize/umzug/issues/94/events","html_url":"https://github.com/sequelize/umzug/issues/94","id":175451501,"number":94,"title":"Accessing missing properties should give an early sequelize error","user":{"login":"manast","id":95200,"avatar_url":"https://avatars.githubusercontent.com/u/95200?v=3","gravatar_id":"","url":"https://api.github.com/users/manast","html_url":"https://github.com/manast","followers_url":"https://api.github.com/users/manast/followers","following_url":"https://api.github.com/users/manast/following{/other_user}","gists_url":"https://api.github.com/users/manast/gists{/gist_id}","starred_url":"https://api.github.com/users/manast/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/manast/subscriptions","organizations_url":"https://api.github.com/users/manast/orgs","repos_url":"https://api.github.com/users/manast/repos","events_url":"https://api.github.com/users/manast/events{/privacy}","received_events_url":"https://api.github.com/users/manast/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-09-07T09:11:13Z","updated_at":"2016-09-07T09:12:54Z","closed_at":"2016-09-07T09:12:54Z","body":"This may be a fundamental design flaw in Sequelize and impossible to fix, but I think it is important to document it somewhere.\r\n\r\nBasically the problem is when trying to refer to a table column that does not exist in the model. Sequelize does not seem to care to validate its existence before doing a query. This results in the database giving an exception. The problem with this approach is that I loose the ability to know where in my code this invalid query is being performed. I guess the underlying issue here is that since .sync is not really syncing the models with SQL, the developers of Sequelize decided to delegate the validation to the SQL server instead. I do not think this is the correct approach, it seems to be wiser to make the validation before making the query, independently if that column exists in SQL or not. "},"comment":{"url":"https://api.github.com/repos/sequelize/umzug/issues/comments/245222160","html_url":"https://github.com/sequelize/umzug/issues/94#issuecomment-245222160","issue_url":"https://api.github.com/repos/sequelize/umzug/issues/94","id":245222160,"user":{"login":"manast","id":95200,"avatar_url":"https://avatars.githubusercontent.com/u/95200?v=3","gravatar_id":"","url":"https://api.github.com/users/manast","html_url":"https://github.com/manast","followers_url":"https://api.github.com/users/manast/followers","following_url":"https://api.github.com/users/manast/following{/other_user}","gists_url":"https://api.github.com/users/manast/gists{/gist_id}","starred_url":"https://api.github.com/users/manast/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/manast/subscriptions","organizations_url":"https://api.github.com/users/manast/orgs","repos_url":"https://api.github.com/users/manast/repos","events_url":"https://api.github.com/users/manast/events{/privacy}","received_events_url":"https://api.github.com/users/manast/received_events","type":"User","site_admin":false},"created_at":"2016-09-07T09:12:54Z","updated_at":"2016-09-07T09:12:54Z","body":"wrong repo"}}
{"actor":{"display_login":"manast"}}