Re: [IndexedDB] Changing the default overwrite behavior of Put

[Shawn Wilsher]

On 6/16/2010 9:43 AM, Nikunj Mehta wrote:

There are three theoretical modes as you say. However, the second mode does not 
exist in practice. If you must overwrite, then you know that the record exists 
and hence don't need to specify that option.

To be clear, you are saying that there are only two modes in practice:
1) add
2) add or modify

But you don't believe that "modify" doesn't exist in practice? In terms of SQL, these three concepts exists and get used all the time. "add" maps to INSERT INTO, "add or modify" maps to INSERT OR REPLACE INTO, and "modify" maps to UPDATE.

So, in summary, I agree to splitting the put method in to two - put and 
putNoOverwrite. I am also in favor of retaining the name as put (contrasted 
with get). I would like to avoid bikeshedding on names even though there have 
been ample opportunities on this list lately with that.

I think you are completely ignoring the arguments in this thread about the issues with naming it put. I don't think it is bikeshedding; these seem like legitimate concerns.

Cheers,

Shawn

smime.p7s
Description: S/MIME Cryptographic Signature