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
I'm using an ExistsIn build rule with one of my association which has conditions. Since I'm explicitly checking for the existence in an association - not in a table - I would expect ExistsIn to use the association conditions to check for the existence.
My suggestion would be respecting the association conditions, so data integrity will be enforced. If there are conditions on an association which shouldn't be checked (I can't think of a reason for that, to be honest), you could still pass an instance of a table instead of the association name.
What are the opinions on this matter? I would be happy to implement this if you agree on this.
The text was updated successfully, but these errors were encountered:
I'm using an
ExistsIn
build rule with one of my association which has conditions. Since I'm explicitly checking for the existence in an association - not in a table - I would expectExistsIn
to use the association conditions to check for the existence.My suggestion would be respecting the association conditions, so data integrity will be enforced. If there are conditions on an association which shouldn't be checked (I can't think of a reason for that, to be honest), you could still pass an instance of a table instead of the association name.
What are the opinions on this matter? I would be happy to implement this if you agree on this.
The text was updated successfully, but these errors were encountered: