W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2010

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

From: Jonas Sicking <jonas@sicking.cc>
Date: Wed, 16 Jun 2010 11:08:38 -0700
Message-ID: <AANLkTil6VqTu-y_XzlqGdxOyj0paDhDny43fOpRbJXpS@mail.gmail.com>
To: Nikunj Mehta <nikunj@o-micron.com>
Cc: Shawn Wilsher <sdwilsh@mozilla.com>, Kris Zyp <kris@sitepen.com>, public-webapps WG <public-webapps@w3.org>
On Wed, Jun 16, 2010 at 10:46 AM, Nikunj Mehta <nikunj@o-micron.com> wrote:
>
> On Jun 16, 2010, at 9:58 AM, Shawn Wilsher wrote:
>
>> 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.
>
> IndexedDB is not SQL, I think you would agree. UPDATE is useful when you replace on a column, by column basis and, hence, need to do a blind update. When updating a record in IndexedDB, you'd have to be certain about the state of the entire record. Hence, it makes sense to leave out UPDATE semantics in IndexedDB.

I can't say that I have a strong sense of if "modify" is needed or
not. On the surface if seems strange to leave out, but it's entirely
possible that it isn't needed.

Unless someone provides a good use case, I would be fine with leaving
it out and seeing if people ask for it.

/ Jonas
Received on Wednesday, 16 June 2010 18:09:33 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:39 GMT