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

[Bug 9769] New: IDBObjectStoreRequest/Sync.put should be split into 3 methods

From: <bugzilla@jessica.w3.org>
Date: Wed, 19 May 2010 11:08:49 +0000
To: public-webapps@w3.org
Message-ID: <bug-9769-2927@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9769

           Summary: IDBObjectStoreRequest/Sync.put should be split into 3
                    methods
           Product: WebAppsWG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: WebSimpleDB
        AssignedTo: nikunj.mehta@oracle.com
        ReportedBy: jorlow@chromium.org
         QAContact: member-webapi-cvs@w3.org
                CC: mike@w3.org, public-webapps@w3.org


IDBObjectStoreRequest/Sync.put currently takes an optional parameter
"noOverwrite"  But as was discussed in "[IndexedDB] Changing the default
overwrite behavior of Put" [1] what we really need is a tri-state: only insert,
only modify, or either.  Maciej suggested we should just have 3 separate
functions.  This was re-iterated with Mozilla's proposal (well, 3 guys _from_
Mozilla's proposal :-) in ""[IndexDB] Proposal for async API changes" [2].

I think the current leading proposal naming wise is "add/modify/addOrModify". 
It's unfortunate that the common case (addOrModify) is the most verbose one,
but as discussed in the second thread, it's the most clear set of names
anyone's proposed so far.

[1] http://www.mail-archive.com/public-webapps@w3.org/msg08646.html
[2] http://www.mail-archive.com/public-webapps@w3.org/msg08825.html

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Wednesday, 19 May 2010 11:08:51 GMT

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