The exclude_output_inserted_table_names feature does not handle composite primary keys with defferent data types properly.
Expected behavior
The exclude_output_inserted_table_names should be able to handle composite primary keys of different data types without errors.
Actual behavior
Currently, if you try to use exclude_output_inserted_table_names for a table with a composite primary key, this setting will not handle the scenario correctly. This limitation makes it particularly difficult to manage tables with composite keys containing different data types.
How to reproduce
Create a table with a composite primary key where the keys have different data types and attempt to insert data using the ActiveRecord-SQLServer adapter with exclude_output_inserted_table_names configured. Here is an example setup that triggers the error:
create_table "SampleTable", primary_key: ["KeyPart1", "KeyPart2"], force: :cascade do |t|
t.uuid "KeyPart1", null: false
t.integer "KeyPart2", null: false # different data type
end
Issue
The exclude_output_inserted_table_names feature does not handle composite primary keys with defferent data types properly.
Expected behavior
The exclude_output_inserted_table_names should be able to handle composite primary keys of different data types without errors.
Actual behavior
Currently, if you try to use exclude_output_inserted_table_names for a table with a composite primary key, this setting will not handle the scenario correctly. This limitation makes it particularly difficult to manage tables with composite keys containing different data types.
How to reproduce
Create a table with a composite primary key where the keys have different data types and attempt to insert data using the ActiveRecord-SQLServer adapter with exclude_output_inserted_table_names configured. Here is an example setup that triggers the error:
Attempting to insert data into this table results in the following error:
Details
7.1.3.2
7.1.3
2.1.7