Skip to content

Coerce test with trigger to autopopulate primary key on insert #1186

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jun 8, 2024

Conversation

aidanharan
Copy link
Contributor

@aidanharan aidanharan commented May 21, 2024

Coerce PersistenceTest#test_model_with_no_auto_populated_fields_still_returns_primary_key_after_insert.

https://github.com/rails-sqlserver/activerecord-sqlserver-adapter/actions/runs/9172172552/job/25218095721

 3) Error:
PersistenceTest#test_model_with_no_auto_populated_fields_still_returns_primary_key_after_insert:
ActiveRecord::NotNullViolation: TinyTds::Error: Cannot insert the value NULL into column 'id', table 'activerecord_unittest.dbo.pk_autopopulated_by_a_trigger_records'; column does not allow nulls. INSERT fails.

@aidanharan aidanharan changed the title Add trigger to autopopulate primary key on insert Coerce test with trigger to autopopulate primary key on insert Jun 8, 2024
@aidanharan aidanharan marked this pull request as ready for review June 8, 2024 17:00
@aidanharan aidanharan merged commit ccb357b into main Jun 8, 2024
2 of 8 checks passed
@aidanharan aidanharan deleted the pk_autopopulated_trigger branch June 8, 2024 17:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant