9882 2010-06-08 17:22:42 +0000 Behavior when attempting to write data to an objectStore opened as read only unspecified 2010-11-08 18:15:18 +0000 1 1 1 Unclassified WebAppsWG Indexed Database API unspecified PC All RESOLVED FIXED P2 normal --- 1 jorlow nikunj.mehta jonas jorlow mike public-webapps sdwilsh public-webapps-bugzilla oldest_to_newest 36051 0 jorlow 2010-06-08 17:22:42 +0000 When you open an objectStore with a read only mode, any subsequent write operation should probably result in an error. I don't see anywhere in the spec that specifically says this or mentions what error code should be used. Currently in the spec, writing with the noOverwrite flag set causes a CONSTRAINT_ERR, so I'm guessing that's the best one to go with for this condition as well? 42281 1 jonas 2010-11-08 18:14:18 +0000 I introduced a specific READ_ONLY_ERR to cover this. It seems worth having a separate error rather than throwing NOT_ALLOWED_ERR since it's a very easy mistake to make to forget to specify the optional 'mode' parameter when creating a transaction, and so I think it's worth making this error easy to diagnose. http://dvcs.w3.org/hg/IndexedDB/rev/0901d0b89904 42282 2 jonas 2010-11-08 18:15:18 +0000 I introduced a specific READ_ONLY_ERR to cover this. It seems worth having a separate error rather than throwing NOT_ALLOWED_ERR since it's a very easy mistake to make to forget to specify the optional 'mode' parameter when creating a transaction, and so I think it's worth making this error easy to diagnose. http://dvcs.w3.org/hg/IndexedDB/rev/0901d0b89904