#82 closed defect (released)
Existing values are not update by document.add_value()
Reported by: | Mike Trinkala | Owned by: | Olly Betts |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Library API | Version: | 0.9.5 |
Severity: | normal | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Operating System: | Linux |
Description
If I call add_value on an existing value without calling remove first the value is not changed when the document is replaced (per add_value documentation)
Xapian::Document doc = db.get_document(1); string oldstr = doc.get_value(0); "1111111111" is returned string newstr = "1112223334"; doc.remove_value(0); without this remove the value is not replaced doc.add_value(0, newstr); db.replace_document(1, doc); db.flush();
Query doc 1. Without the remove_value call "1111111111" is returned
Additional Info
Fedora Core 5, Flint Backend
Change History (3)
comment:1 by , 18 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:2 by , 18 years ago
Oh yes, the diff is here:
http://xapian.org/C?7045?trunk/xapian-core/api/omdocument.cc
comment:3 by , 18 years ago
Operating System: | → Linux |
---|---|
Resolution: | fixed → released |
Note:
See TracTickets
for help on using tickets.
Thanks for reporting this. I've just committed a fix to SVN HEAD.