GNOME Bugzilla – Bug 689033
symbol-db: When updating a symbol try to update the closest one.
Last modified: 2012-12-23 10:45:37 UTC
See the attached patch.
Created attachment 229826 [details] [review] symbol-db: When updating a symbol try to update the closest one. This way we get rid of alot of warnings like this: (lt-anjuta:27226): libanjuta-symbol-db-WARNING **: SQL execute_non_select failed: columns name, file_defined_id, file_position are not unique which was caused by updating two symbols that has the same name but is at different file positions. Previously it could happen that we updated the first symbol with the file position of the second which caused the unique constraint to fail.
*** Bug 690314 has been marked as a duplicate of this bug. ***
Comment on attachment 229826 [details] [review] symbol-db: When updating a symbol try to update the closest one. I've committed the patch. Can you please rename the function sdb_engine_get_tuple_id_by_unique_name4 to sdb_engine_get_tuple_id_by_unique_name5 so that it reflects that it's taking 5 key-value parameters? Thanks
Created attachment 232135 [details] [review] symbol-db: rename sdb_engine_get_tuple_id_by_unique_name4()... to sdb_engine_get_tuple_id_by_unique_name5() since it now takes five parameters.
thanks, patch applied. I'm closing the bug.