Open jtpavlock opened 2 years ago
I have the same issue in SQLModel 0.08 and it's kind of a big deal. Is there a workaround for this besides re-assigning the entire dict i.e. good_track.custom = {"test": changed"}
?
Any update here, A big blocker before I can migrate from sqlalchemy+pydantic to sqlmodel.
Also a blocker here, commenting to stay in the loop!
yep, same here, blocker.
First Check
Commit to Help
Example Code
Description
When setting a field to one of the fields supported by sqlalchemy mutation tracking, it seems the mutation tracking isn't working as intended. I attached the above code sample to illustrate what I mean. The assertions on the bottom of the script should pass under normal circumstance.
Operating System
Linux
Operating System Details
No response
SQLModel Version
0.08
Python Version
3.9.13
Additional Context
No response