mirror of
https://github.com/appy-one/acebase.git
synced 2026-05-25 06:02:14 -06:00
[GH-ISSUE #75] Sorting with indexed field #51
Labels
No labels
IndexedDB
browser
bug
dependencies
documentation
duplicate
enhancement
feature request
indexes
indexes
invalid
pull-request
query
question
transaction logging
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/acebase#51
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @paradis-A on GitHub (Feb 23, 2022).
Original GitHub issue: https://github.com/appy-one/acebase/issues/75
Originally assigned to: @appy-one on GitHub.
Using v1.15.0
load first 100 sort letter by a-z (non-indexed)
√ (547ms)
load second 100 sort letter by a-z (non-indexed)
√ (345ms)
load third 100 sort letter by a-z (non-indexed)
√ (325ms)
load first 100 sort letter by z-a (non-indexed)
√ (254ms)
load second 100 sort letter by z-a (non-indexed)
√ (283ms)
load third 100 sort letter by z-a (non-indexed)
√ (300ms)
load first 100 sort letter by a-z (indexed)
1)
load second 100 sort letter by a-z (indexed)
Lock "./take_test.acebase/sort_indexed-letter.idx" timed out! lock.release() was not called in a timely fashion
2)
load third 100 sort letter by a-z (indexed)
3)
load first 100 sort letter by z-a (indexed)
Lock "./take_test.acebase/sort_indexed-letter.idx" timed out! lock.release() was not called in a timely fashion
4)
load second 100 sort letter by a-z (indexed)
5)
load third 100 sort letter by a-z (indexed)
Lock "./take_test.acebase/sort_indexed-letter.idx" timed out! lock.release() was not called in a timely fashion
6)
6 passing (3m)
6 failing
load first 100 sort letter by a-z (indexed)
:
Error: Error: ext_data values were not read yet. use entry.extData.loadValues() first
at C:\System\lenlen\lendb-server\node_modules\acebase-core\dist\data-reference.js:845:19
at async Context. (acebasetake.spec.js:105:9)
load second 100 sort letter by a-z (indexed)
:
Error: Error: Could not achieve lock because the current lock ("./take_test.acebase/sort_indexed-letter.idx") was not released in time (and lock is flagged critical)
at C:\System\lenlen\lendb-server\node_modules\acebase-core\dist\data-reference.js:845:19
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async Context. (acebasetake.spec.js:113:9)
load third 100 sort letter by a-z (indexed)
:
Error: Error: ext_data values were not read yet. use entry.extData.loadValues() first
at C:\System\lenlen\lendb-server\node_modules\acebase-core\dist\data-reference.js:845:19
at async Context. (acebasetake.spec.js:121:9)
load first 100 sort letter by z-a (indexed)
:
Error: Error: Could not achieve lock because the current lock ("./take_test.acebase/sort_indexed-letter.idx") was not released in time (and lock is flagged critical)
at C:\System\lenlen\lendb-server\node_modules\acebase-core\dist\data-reference.js:845:19
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async Context. (acebasetake.spec.js:130:9)
load second 100 sort letter by a-z (indexed)
:
Error: Error: ext_data values were not read yet. use entry.extData.loadValues() first
at C:\System\lenlen\lendb-server\node_modules\acebase-core\dist\data-reference.js:845:19
at async Context. (acebasetake.spec.js:138:9)
load third 100 sort letter by a-z (indexed)
:
Error: Error: Could not achieve lock because the current lock ("./take_test.acebase/sort_indexed-letter.idx") was not released in time (and lock is flagged critical)
at C:\System\lenlen\lendb-server\node_modules\acebase-core\dist\data-reference.js:845:19
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async Context. (acebasetake.spec.js:146:9)
@paradis-A commented on GitHub (Feb 23, 2022):
full test code:
@appy-one commented on GitHub (Feb 23, 2022):
Fixed! Published with v1.15.1
Thanks for your report & tests @paradis-A 👍🏼