-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LibSQL: Persisted tables with a large number of columns corrupt the database #15844
Labels
Comments
gmta
added a commit
to gmta/serenity
that referenced
this issue
Nov 26, 2022
After splitting a node, the new node was written to the same pointer as the current node - probably a copy / paste error. This new code requires a `.pointer() -> u32` to exist on the object to be serialized, preventing this issue from happening again. Fixes SerenityOS#15844.
gmta
added a commit
to gmta/serenity
that referenced
this issue
Nov 26, 2022
After splitting a node, the new node was written to the same pointer as the current node - probably a copy / paste error. This new code requires a `.pointer() -> u32` to exist on the object to be serialized, preventing this issue from happening again. Fixes SerenityOS#15844.
gmta
added a commit
to gmta/serenity
that referenced
this issue
Nov 26, 2022
After splitting a node, the new node was written to the same pointer as the current node - probably a copy / paste error. This new code requires a `.pointer() -> u32` to exist on the object to be serialized, preventing this issue from happening again. Fixes SerenityOS#15844.
awesomekling
pushed a commit
that referenced
this issue
Nov 26, 2022
After splitting a node, the new node was written to the same pointer as the current node - probably a copy / paste error. This new code requires a `.pointer() -> u32` to exist on the object to be serialized, preventing this issue from happening again. Fixes #15844.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We seem to have invalid data from a persisted DB when it contains a table with a "large" (~12) number of columns. For example, trying to
DESCRIBE
that table, the privatemaster.internal_describe_table
used forDESCRIBE
should have 2 columns itself, but has 0 (m_data.size()
in the below assertion is 0).To repro, add this to Tests/LibSQL/TestSqlStatementExecution.cpp:
I've been investigating it on this branch: https://github.com/trflynn89/serenity/tree/sql_boomEDIT: The fixes from that branch were merged in #15865.
But I'm not making much progress so maybe someone else has some ideas :)
The text was updated successfully, but these errors were encountered: