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

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

From: Jeremy Orlow <jorlow@chromium.org>
Date: Mon, 10 May 2010 09:33:50 +0100
Message-ID: <AANLkTikjAorzwbX1X_yMFNF3gNthGlABjdYrUK2BK8eM@mail.gmail.com>
To: ben turner <bent.mozilla@gmail.com>
Cc: public-webapps WG <public-webapps@w3.org>
Either sounds fine to me.  Please open something in the bug tracker?

On Fri, May 7, 2010 at 10:12 PM, ben turner <bent.mozilla@gmail.com> wrote:

> I think that switching 'noOverwrite' from false to true is confusing.
> I definitely vote to rename the parameter to 'overwrite' and and keep
> the default as false.
>
> -Ben
>
> On Fri, May 7, 2010 at 12:32 PM, Shawn Wilsher <sdwilsh@mozilla.com>
> wrote:
> > Hey all,
> >
> > Per the current spec [1], noOverwrite defaults to false for put
> operations
> > on an object store.  Ben Turner and I have been discussing changing the
> > default of put to not allow overwriting by default.  We feel this is
> better
> > behavior because simply omitting the flag should not result in destroying
> > data.  Putting my application developer hat on, I'd much rather have to
> be
> > explicit about destroying existing data instead of having it happen on
> > accident.  We could also change the parameter to just overwrite and have
> it
> > default to false.
> >
> > What is everyone's thoughts on this?
> >
> > Cheers,
> >
> > Shawn
> >
> >
>
>
Received on Monday, 10 May 2010 08:34:43 GMT

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