Active
Project:
Similarity Objects
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
18 Mar 2009 at 22:26 UTC
Updated:
24 Mar 2009 at 08:07 UTC
db_query needed a float (%f).
| Comment | File | Size | Author |
|---|---|---|---|
| similarity_Cleanup_Fix.patch | 703 bytes | Büke Beyond |
Comments
Comment #1
Scott Reynolds commentedI really don't like this solution still, need to examine the need for the clean_up() function. There is a strong possibility for stale similarity data to reside in the table. So the easiest option is to insert into the similarity table all values regardless of how dissimilar and then call the clean_up() function to delete the dissimilar items.
If you don't do that, you have the possibility of having a once very similar relationship but over time became dissimilar. These are never cleaned up. Wonder if there is a way to use a timestamp to expire the relationships over time. Most similarity handlers will use an INSERT () ON DUPLICATE KEY UPDATE clauses, so it could update the timestamp stuff. Thus allowing a relationship to expire.