Bug 209429

Summary: IDBObjectStore.openCursor() fails if 'prevunique' or 'nextunique' direction is provided
Product: WebKit Reporter: Jamie Gaehring <gaehj457>
Component: New BugsAssignee: Nobody <webkit-unassigned>
Status: CLOSED WORKSFORME    
Severity: Normal CC: bfulgham, sihui_liu, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: Safari 13   
Hardware: All   
OS: All   
Attachments:
Description Flags
Screenshot of error none

Description Jamie Gaehring 2020-03-23 10:11:11 PDT 
Created attachment 394272 [details]
Screenshot of error

See attachment, or https://github.com/farmOS/farmOS-client/issues/324#issuecomment-602257450. 

This may be related too: https://github.com/periodo/periodo-client/issues/228

I was able to workaround the bug by using 'prev' instead of 'prevunique', but that is not ideal.
Comment 1 Radar WebKit Bug Importer 2022-06-30 15:11:30 PDT 
<rdar://problem/96249170>
Comment 2 Sihui Liu 2022-07-01 16:11:32 PDT 
I am not able to reproduce the case where we cannot create "prevunique" cursor. According to the error from the screenshot, it should be failure in SQLiteIDBTransaction::maybeOpenCursor; but I am not sure how it's related to unique.

As this bug was reported a long time ago (there were changes around IDBCursor during this time), and I am not able to reproduce on truck, I am going to close this bug.

Jamie, if you can still reproduce the bug in recent Safari, please re-open this bug with reproduce steps and test cases.
Comment 3 Jamie Gaehring 2022-07-01 16:34:07 PDT 
(In reply to Sihui Liu from comment #2)
> I am not able to reproduce the case where we cannot create "prevunique"
> cursor. According to the error from the screenshot, it should be failure in
> SQLiteIDBTransaction::maybeOpenCursor; but I am not sure how it's related to
> unique.
> 
> As this bug was reported a long time ago (there were changes around
> IDBCursor during this time), and I am not able to reproduce on truck, I am
> going to close this bug.
> 
> Jamie, if you can still reproduce the bug in recent Safari, please re-open
> this bug with reproduce steps and test cases.

I have not seen issues related to this recently, so just as well to leave it closed. Thank you!