Hitting "NoMethodError" for find_by_<x> with a view as a table.

[napcs]

We've had a SQLServer view we've used with this adapter for several years now. With my tests this morning, we can retrieve data with things like .first and .last, but none of the dynamic finders like

find_by_username

and others fail to work - we get "method not found" errors.

This is a legacy table with a very ugly schema so we've used a view to remap it.

class PersonRecord < ActiveRecord::Base
  set_table_name "person_record"
  set_primary_key "personid"
end

This seems to happen with Rails 3 as well. This is with TDS and I tested this on Rails 3.0.9 with sqlserver-adapter 3.0.15 and on Rails 3.1 with sqlserver-adapter 3.1.0.

I cannot get dbi and friends working with Rails 3 - getting all sorts of nomethod errors related to DBI::Date. Our Rails 2 apps that work use sqlserver-adapter + odbc, so I cannot say for sure if the problem is a change made in sqlserver adapter or with FreeTDS and views.

[metaskills]

First, DBI has been out of the 2-3-stable and 3.(0 or 1) branches for some time. It has no usage in our code base under each latest version. Second, you'll need to be specific on where this bug exists? 2-3-stable? master, etc and where it stopped working. FWIW, we have always passed the AR tests and our own which include dynamic finders. I do not know if we have tests in our base that extend a few assertions to views like that.

We do have this context for views where we try to make sure we are doing things to make views 100% act like standard tables. So this is a good place to write a regression test.
https://github.com/rails-sqlserver/activerecord-sqlserver-adapter/blob/master/test/cases/adapter_test_sqlserver.rb#L513

BTW, I do know that we had a good amount of work in all major branches 2-3-stable and 3.1 to better cope with proper schema support. IE, making sure we get column objects back for a table/view in the correct schema. Perhaps you are now seeing where columns are not defined properly for the view due to that? Let me know if you need more help tracking this down. If you can write a regression test in that context that fails, I would love to get this patched.

[napcs]

Closing this since I believe it's related to #118.

As I said there, not using DBI, but only reverted to it when tinytds wasn't fetching records and I wanted to eliminate the possibility that it was a tinytds issue.