On run command
/usr/bin/clamsbsync.py -v --config /etc/clamav/safebrowsing.conf --logfile /var/log/safebrowsing.log sync
return this error
/usr/bin/clamsbsync.py:22: SAWarning: relationship 'SBPrefix.hashes' will copy column sbclient_v4_prefixes.reflist_id to column sbclient_v4_hashes.reflist_id, which conflics 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 shouldbe 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 partialy 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="hashe"' to the 'SBPrefix.hashes' relationship. (Background on this error at: https://sqlalche.me/e/14/qzyx)
state = "",
/usr/bin/clamsbsync.py:22: SAWarning: relationship 'SBHash.reflist' will copy column sbclient_v4_lists.id to column sbclient_v4_hashes.reflist_id, which conflicts with relaionship(s): 'SBPrefix.hashes' (copies sbclient_v4_prefixes.reflist_id to sbclient_v4_hashes.reflist_id). If this is not the intention, consider if these relationships shoul 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 partialy 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="hashs"' to the 'SBHash.reflist' relationship. (Background on this error at: https://sqlalche.me/e/14/qzyx)
state = "",
On run command /usr/bin/clamsbsync.py -v --config /etc/clamav/safebrowsing.conf --logfile /var/log/safebrowsing.log sync
return this error
/usr/bin/clamsbsync.py:22: SAWarning: relationship 'SBPrefix.hashes' will copy column sbclient_v4_prefixes.reflist_id to column sbclient_v4_hashes.reflist_id, which conflics 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 shouldbe 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 partialy 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="hashe"' to the 'SBPrefix.hashes' relationship. (Background on this error at: https://sqlalche.me/e/14/qzyx) state = "", /usr/bin/clamsbsync.py:22: SAWarning: relationship 'SBHash.reflist' will copy column sbclient_v4_lists.id to column sbclient_v4_hashes.reflist_id, which conflicts with relaionship(s): 'SBPrefix.hashes' (copies sbclient_v4_prefixes.reflist_id to sbclient_v4_hashes.reflist_id). If this is not the intention, consider if these relationships shoul 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 partialy 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="hashs"' to the 'SBHash.reflist' relationship. (Background on this error at: https://sqlalche.me/e/14/qzyx) state = "",