[GH-ISSUE #110] Max storage recordSize and/or pageSize (65536) not working #61

New issue

Closed

opened 2026-05-23 08:28:43 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-23 08:28:43 -06:00

Owner

Originally created by @appy-one on GitHub (May 25, 2022).
Original GitHub issue: https://github.com/appy-one/acebase/issues/110

Originally assigned to: @appy-one on GitHub.

When setting the recordSize or pageSize to the max of 65536 (2¹⁶) in the storage settings, the created db doesn't work. Because the value 2¹⁶ requires a 17th bit to store 1 followed by 16 zeroes, the settings written to the file are 16 bit and become 0. Because a recordSize of 0 does not store any data, this is a very quick dead end.

const db = new AceBase('mydb', { storage: { recordSize: 65536 } }); // Problem!

To fix this I will be treating a recordSize and/or pageSize of 0 in the file as the max of 65536.

Originally created by @appy-one on GitHub (May 25, 2022). Original GitHub issue: https://github.com/appy-one/acebase/issues/110 Originally assigned to: @appy-one on GitHub. When setting the `recordSize` or `pageSize` to the max of 65536 (2<sup>16</sup>) in the `storage` settings, the created db doesn't work. Because the value 2<sup>16</sup> requires a 17th bit to store 1 followed by 16 zeroes, the settings written to the file are 16 bit and become 0. Because a recordSize of 0 does not store any data, this is a very quick dead end. ```js const db = new AceBase('mydb', { storage: { recordSize: 65536 } }); // Problem! ``` To fix this I will be treating a recordSize and/or pageSize of 0 in the file as the max of 65536.