Error when performing SQL insert in cross database scenario.

[chrisortman]

I believe this is the culprit.

activerecord-sqlserver-adapter/lib/active_record/connection_adapters/sqlserver/database_statements.rb

Line 482 in 0adea5b

id_column = identity_columns(raw_table_name).first

When you leverage the capability of SQL Server to operate across databases the lookup for identity columns is broken because schema_cache is bound to a single connection pool.

Just to illustrate with an example the following can be added to line 84 of adapter_test_sqlserver.rb

    sql = <<~SQL
    INSERT INTO #{arunit2_database}.dbo.colleges SELECT * FROM #{arunit_database}.dbo.topics
    SQL

    assert arunit_connection.send(:query_requires_identity_insert?, sql)

[aidanharan]

Could you create a script to reproduce the issue? See https://github.com/rails-sqlserver/activerecord-sqlserver-adapter/wiki/How-to-report-a-bug

[chrisortman]

Yup, working on it ....running into weird platform issues with sqlite3 gem. My RUBY_PLATFORM is aarch64-linux but the gem is locked to aarch64-linux-{gnu,musl}

Going to try adding aarch64-linux to the lock file and see if that works.

Problem is strange because sometimes bundle install works and I'd expect it to always fail. But I had run the test suite before I submitted the bug report.

[chrisortman]

I should be able to get you a PR with a fix along with the test. I'd like to change identity_columns to only return the column names instead of a column object, is that OK? This is so that I can go directly to the database to get the identity columns instead of use schema_cache