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 have just updated to piecash 1.2.1 and SQLAlchemy 1.4 and see many warnings, e.g.
piecash\core\session.py:442: SAWarning: relationship 'Account.slots' will copy column accounts.guid to column slots.obj_guid, which conflicts with relationship(s): 'Slot.parent' (copies slots.guid_val to slots.obj_guid), 'SlotFrame.slots' (copies slots.guid_val to slots.obj_guid). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="parent,slots"' to the 'Account.slots' relationship. (Background on this error at: https://sqlalche.me/e/14/qzyx)
for v in s.query(Version).all()
The other warnings all look similar to this one, but with other relationships. Is it safe to ignore these warnings? How difficult would it be to fix the warnings?
The text was updated successfully, but these errors were encountered:
I have just updated to piecash 1.2.1 and SQLAlchemy 1.4 and see many warnings, e.g.
The other warnings all look similar to this one, but with other relationships. Is it safe to ignore these warnings? How difficult would it be to fix the warnings?
The text was updated successfully, but these errors were encountered: