{"issue":{"pull_request":{"diff_url":null,"html_url":null,"patch_url":null},"state":"closed","user":{"avatar_url":"https://secure.gravatar.com/avatar/c44582dd5ee166ebd81fbe9d1ce6200e?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"c44582dd5ee166ebd81fbe9d1ce6200e","url":"https://api.github.com/users/steveo7","login":"steveo7","id":622015},"milestone":null,"assignee":null,"updated_at":"2011-11-08T12:39:47Z","labels":[],"comments":7,"closed_at":"2011-11-02T17:09:01Z","url":"https://api.github.com/repos/rails-sqlserver/activerecord-sqlserver-adapter/issues/140","body":"Thanks for all your work on this adapter.  I am starting a new project using Rails 3.1.1 after prototyping with Rails 3.0.7 and ran into a problem with the .find method.  This is against a legacy schema using views.  \r\n\r\nI am finding that the Activerecord .find method is not working on a view with Rails 3.1.1 and activerecord-sqlserver-adapter 3.1.3. It works okay on the same view with Rails 3.0.7 and activerecord-sqlserver-adapter 3.0.14.  \r\n\r\nRails 3.1.1 \r\nIf run this from the console;\r\nfund = Find.find('A105') \r\nIt returns an error \"RuntimeError: Unknown bind columns. We can account for this.\"\r\nIf I instead use;\r\nfund = Find.find_by_id('A105') it works ok.\r\n\r\n","html_url":"https://github.com/rails-sqlserver/activerecord-sqlserver-adapter/issues/140","number":140,"title":".find() method not working","id":2096803,"created_at":"2011-10-31T13:18:13Z"},"action":"created","comment":{"user":{"avatar_url":"https://secure.gravatar.com/avatar/802f7b7813d7c349a84d444d43cb31ee?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"802f7b7813d7c349a84d444d43cb31ee","url":"https://api.github.com/users/metaskills","login":"metaskills","id":2381},"updated_at":"2011-11-08T12:39:47Z","url":"https://api.github.com/repos/rails-sqlserver/activerecord-sqlserver-adapter/issues/comments/2666970","body":"Thanks, good to know there is a workaround, I wish however I could reproduce this as I think it is a schema reflection issue. Perhaps #column_definitions is not returning identity or primary key information back correctly in some view cases.","id":2666970,"created_at":"2011-11-08T12:39:47Z"}}