Thanks guys,
I'm more inclined to have an API like get_original_metadata and
get_metadata. The get_metadata in this case always returns whatever
metadata is set on the object, new or original. In the current API, if
calling get_update_metadata will return the original metadata if there are
no ch
Reid,
I do understand why update_metadata exists. I guess what I'm
suggesting is a better default behavior, especially for users who
don't explicitly set any metadata values. (Or even if they do, for
when all the metadatas are equivalent.)
I.e., something like this for riakc_obj:get_update_metada
On Jun 12, 2012, at 2:56 PM, Michael Radford wrote:
> get_metadata returns the metadata that was read from riak. But if
> allow_mult is true, and there is more than one sibling, then
> get_metadata throws the exception 'siblings'. You have to call
> get_metadatas to get a list with metadata for e
get_metadata returns the metadata that was read from riak. But if
allow_mult is true, and there is more than one sibling, then
get_metadata throws the exception 'siblings'. You have to call
get_metadatas to get a list with metadata for each sibling in that
case.
get_update_metadata returns the met
