{"action":"opened","issue":{"url":"https://api.github.com/repos/jinzhu/gorm/issues/1258","repository_url":"https://api.github.com/repos/jinzhu/gorm","labels_url":"https://api.github.com/repos/jinzhu/gorm/issues/1258/labels{/name}","comments_url":"https://api.github.com/repos/jinzhu/gorm/issues/1258/comments","events_url":"https://api.github.com/repos/jinzhu/gorm/issues/1258/events","html_url":"https://github.com/jinzhu/gorm/issues/1258","id":188624789,"number":1258,"title":"How to use explicit column names in SELECT queries?","user":{"login":"AA33","id":883671,"avatar_url":"https://avatars.githubusercontent.com/u/883671?v=3","gravatar_id":"","url":"https://api.github.com/users/AA33","html_url":"https://github.com/AA33","followers_url":"https://api.github.com/users/AA33/followers","following_url":"https://api.github.com/users/AA33/following{/other_user}","gists_url":"https://api.github.com/users/AA33/gists{/gist_id}","starred_url":"https://api.github.com/users/AA33/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/AA33/subscriptions","organizations_url":"https://api.github.com/users/AA33/orgs","repos_url":"https://api.github.com/users/AA33/repos","events_url":"https://api.github.com/users/AA33/events{/privacy}","received_events_url":"https://api.github.com/users/AA33/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-11-10T21:36:19Z","updated_at":"2016-11-10T21:36:19Z","closed_at":null,"body":"I'm using GORM for mapping MySQL DB tables which may have extra columns that are not part of the GORM models for them.\r\n\r\nSelecting any row form such a table crashes because GORM emits a SELECT * FROM ... query and tries to scan the results in the model struct which is obviously impossible because there are more returned columns than expected.\r\n\r\nIs there a way to force GORM to explicitly name the columns in the emitted SELECT queries?"}}
{"actor":{"display_login":"AA33"}}