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
Hello,
thank you for creating this simple, yet useful tool.
I came across a situation when I would like to apply fixtures on already filled database (by previously applied fixtures or migrations) to add new data, but in that case it ends up with IntegrityError due to duplicate key (actually the whole record is same).
For such case, I would like to have an option to either ignore conflicts or update record (in eventual case of changed previously applied fixtures). I think it could be seamlessly done similar way as ignoring foreign key checks is implemented.
If you don't mind, I could prepare pull request for that ;)
The text was updated successfully, but these errors were encountered:
Hello,
thank you for creating this simple, yet useful tool.
I came across a situation when I would like to apply fixtures on already filled database (by previously applied fixtures or migrations) to add new data, but in that case it ends up with IntegrityError due to duplicate key (actually the whole record is same).
For such case, I would like to have an option to either ignore conflicts or update record (in eventual case of changed previously applied fixtures). I think it could be seamlessly done similar way as ignoring foreign key checks is implemented.
If you don't mind, I could prepare pull request for that ;)
The text was updated successfully, but these errors were encountered: