-
Notifications
You must be signed in to change notification settings - Fork 2.4k
[Serializer] Lambda Compatibilty Fix #17428
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a way to include the serialised plan (and reproduction) in this PR? How do we do this with other serialised plans? Do we have a folder for this similar to the data
folder for files with the older storage format?
I'd like to see some type of test in this PR.
We would need to run an older DuckDB version that reads a database file produced by a new DuckDB version. This is possible but that doesn't exist in our test suite right now. For this PR, maybe we can add a test that creates a view in a persistent database that has a |
Thanks for your feedback! I've added a test that attaches an older storage version. |
2fbea7e
to
a765001
Compare
I removed the conditional, so now |
Thanks! |
[Serializer] Lambda Compatibilty Fix (duckdb/duckdb#17428)
[Serializer] Lambda Compatibilty Fix (duckdb/duckdb#17428)
[Serializer] Lambda Compatibilty Fix (duckdb/duckdb#17428)
#16602 introduced a new member to
ListLambdaBindData
; however, a default value was not set for the serializer/deserializer, which made it incompatible with previous versions. This has now been fixed.