Skip to content
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

Fix #5730: document older DuckDB versions internally, and state which DuckDB version a specific file came from #5758

Merged
merged 2 commits into from
Dec 21, 2022

Conversation

Mytherin
Copy link
Collaborator

This PR adapts the error message thrown when opening an older version of DuckDB by notifying the user which DuckDB version was used to create a specific file, e.g.:

$ duckdb test/storage/bc/db_04.db
Error: unable to open database "test/storage/bc/db_04.db": IO Error: Trying to read a database file with version number 33, but we can only read version 40.
The database file was created with DuckDB version v0.3.3, v0.3.4 or v0.4.0.

The storage of DuckDB is not yet stable; newer versions of DuckDB cannot read old database files and vice versa.
The storage will be stabilized when version 1.0 releases.

For now, we recommend that you load the database file in a supported version of DuckDB, and use the EXPORT DATABASE command followed by IMPORT DATABASE on the current version of DuckDB.

See the storage page for more information: https://duckdb.org/internals/storage

We also link to the new storage info page which documents the storage version further.

@Mytherin Mytherin merged commit a133a60 into duckdb:master Dec 21, 2022
@Mytherin Mytherin deleted the storageversion branch January 7, 2023 15:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant