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
We have a model where the import behavior is inconsistent in populating an enum value with the INSERT INTO statement where sometimes it has it, and other times it does not.
If I try to import them directly in one context, you can see that rather than setting 0 for the enum it sets NULL (it doesn't make a difference if I choose a different value):
We have a model where the
import
behavior is inconsistent in populating anenum
value with theINSERT INTO
statement where sometimes it has it, and other times it does not.Here is the model definition:
If I try to import them directly in one context, you can see that rather than setting
0
for the enum it setsNULL
(it doesn't make a difference if I choose a different value):But in other contexts like doing a
recursive: true
it does get itJust trying to think through anything to try that might drive this behavior.
The text was updated successfully, but these errors were encountered: