Thanks for the example.
I don't know what has changed, but is it an idea to check for existence before adding?
-jcw
Thanks for the reply. The example was to show that it creates another row with the
same key value in 2.4.9.3. Actually I have been using view.append to 'update' a
row in a hash view. But it no longer works as the old row isn't overwritten.
Now i am forced to shift to a 'native' view and do something like:
new_index = view.append('changed_row')
matching_indices=view.indices(view.select({'key':'row_to_be_updated'})
matching_indices.remove(matching_indices.select({'index':new_index}))
view.remove(matching_indices)
Shift to the native view is forced as after a 'remove' i need to recreate the
hash view for it to recognise the changed row. I mean if i do a
view.find({'key':'row_to_be_updated'}) after the above code, it returns a
failure unless i do view=db.view('my_view') again. I checked this with 2.4.8
and it works fine there.
I am not sure why nobody else has reported this so far. I have tried building
2.4.9.3 from code, with python 2.2 and 2.3 - all with the same results.
Thx again for your time and effort.
Rajeev
_____________________________________________ Metakit mailing list - [EMAIL PROTECTED] http://www.equi4.com/mailman/listinfo/metakit
