There is a bug in the activerecord-sqlserver-adapter-2.2.21 gem.<\/p>\n
The error is in the file:<\/p>\n
\r\n\\lib\\active_record\\connection_adapters\\sqlserver_adapter.rb\r\n<\/pre>\nLine 1058 reads:<\/p>\n
\r\nFROM #{db_name}INFORMATION_SCHEMA.COLUMNS columns\r\n<\/pre>\nBut should read<\/p>\n
\r\nFROM #{db_name}.INFORMATION_SCHEMA.COLUMNS columns\r\n<\/pre>\nThe lack of a full stop between the db_name and INFORMATION_SCHEMA causes an error because the database name gets appended to INFORMATION_SCHEMA and you get an error. For example, if the database was ‘db_one’ you’d get the error:<\/p>\n
\r\nInvalid object name 'db_oneINFORMATION_SCHEMA.COLUMNS'\r\n<\/pre>\nWhen you try a connection.select (e.g. connection.select_all(sql))<\/p>\n
An update<\/em>
\nThere could be an issue with the simple solution of just adding a period. The issue is that if a db_name isn’t speciftied the SQL code could need to be just:<\/p>\nFROM INFORMATION_SCHEMA.COLUMNS columns<\/p>\n
Therefore add a private method to sqlserver_adapter.rb:<\/p>\n
\r\ndef db_name_with_period(db_name)\r\n \"#{db_name}.\"\r\nend\r\n<\/pre>\nAnd then update the problem line to:<\/p>\n
\r\nFROM #{db_name_with_period(db_name) if db_name}INFORMATION_SCHEMA.COLUMNS columns\r\n<\/pre>\nThe problem has been posted to github:<\/p>\n
http:\/\/github.com\/rails-sqlserver\/2000-2005-adapter\/issues\/closed\/#issue\/3<\/a><\/p>\n
update 15-Jan-10<\/strong>
\nThe problem is still present in the latest version of the adapter and therefore I have added a new issue<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"Error causes INFORMATION_SCHEMA.COLUMNS to be appended to database name when using connection.select. Continue reading