Hi, this issue was reported some time ago and is still occurring. Any ideas?
./clamsbwrite.py --config /etc/clamd.d/safebrowsing.conf
./clamsbwrite.py:36: SAWarning: relationship 'SBPrefix.hashes' will copy
column sbclient_v4_prefixes.reflist_id to column
sbclient_v4_hashes.reflist_id, which conflicts with relationship(s):
'SBList.hashes' (copies sbclient_v4_lists.id to
sbclient_v4_hashes.reflist_id). 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="hashes"' to the 'SBPrefix.hashes' relationship.
(Background on this error at: https://sqlalche.me/e/14/qzyx)
lists = session.query(db.SBList).all()
...
https://github.com/Cisco-Talos/clamav-safebrowsing/issues/10
./clamsbwrite.py --config /etc/clamd.d/safebrowsing.conf
./clamsbwrite.py:36: SAWarning: relationship 'SBPrefix.hashes' will copy
column sbclient_v4_prefixes.reflist_id to column
sbclient_v4_hashes.reflist_id, which conflicts with relationship(s):
'SBList.hashes' (copies sbclient_v4_lists.id to
sbclient_v4_hashes.reflist_id). 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="hashes"' to the 'SBPrefix.hashes' relationship.
(Background on this error at: https://sqlalche.me/e/14/qzyx)
lists = session.query(db.SBList).all()
...
https://github.com/Cisco-Talos/clamav-safebrowsing/issues/10