You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This looks potentially problematic to me, but I don't know enough about IndexedDB to be sure, hence the question: can this ever return an incorrect result? Like is it possible that after the key for an object is returned, but before the value for that object is returned, the key gets deleted so that one ends up with the array of keys and the array of values having different lengths, which would potentially completely mess up the database depending on how those entires are manipulated?
The text was updated successfully, but these errors were encountered:
I see the
entries
method basically requests both keys and values and then merges them together:This looks potentially problematic to me, but I don't know enough about IndexedDB to be sure, hence the question: can this ever return an incorrect result? Like is it possible that after the key for an object is returned, but before the value for that object is returned, the key gets deleted so that one ends up with the array of keys and the array of values having different lengths, which would potentially completely mess up the database depending on how those entires are manipulated?
The text was updated successfully, but these errors were encountered: