You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 15, 2021. It is now read-only.
First a bit of context, I have a fabricator for an ActiveRecord model that is backed by a materialized view which has both an id column and pk column (my custom primary key column).
I run into the issue where setting the pk or id results in both fields being set to the same string value, so my id column ends up with a string value when it should be an integer.
First a bit of context, I have a fabricator for an
ActiveRecord
model that is backed by a materialized view which has both anid
column andpk
column (my custom primary key column).I run into the issue where setting the
pk
orid
results in both fields being set to the same string value, so myid
column ends up with a string value when it should be an integer.Ultimately I want to be able to test I get the right data back when I perform a sql join on
id
column of the materialized view.The text was updated successfully, but these errors were encountered: