-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/24/2010 2:10 PM, Jonas Sicking wrote:
On Fri, May 21, 2010 at 6:59 PM, Kris Zyp k...@sitepen.com wrote:
or to use something like
put(record, {forbidOverwrite: true}); // don't overwrite
put(record, {onlyOverwrite: true}); // must
On Fri, May 21, 2010 at 6:59 PM, Kris Zyp k...@sitepen.com wrote:
or to use something like
put(record, {forbidOverwrite: true}); // don't overwrite
put(record, {onlyOverwrite: true}); // must overwrite/update
put(record, {}); or put(record); // can do either
or some such.
However
On Wed, May 19, 2010 at 5:45 AM, Kris Zyp k...@sitepen.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I continue to believe that splitting put into 3 methods is a very
shortsighted approach to dealing with put directives. We are currently
looking at how to indicate whether or not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/21/2010 6:16 PM, Jonas Sicking wrote:
On Wed, May 19, 2010 at 5:45 AM, Kris Zyp k...@sitepen.com
wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
I continue to believe that splitting put into 3 methods is a
very shortsighted approach
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I continue to believe that splitting put into 3 methods is a very
shortsighted approach to dealing with put directives. We are currently
looking at how to indicate whether or not to overwrite an existing
record when putting data in the DB, but there
