-
Notifications
You must be signed in to change notification settings - Fork 0
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
Identify schema version of old spatialites TOPDESK 2406 0054 #241
Comments
leendertvanwolfswinkel
added
bug
Something isn't working
and removed
bug
Something isn't working
labels
Jun 26, 2024
leendertvanwolfswinkel
changed the title
Identify schema version of old spatialites
Identify schema version of old spatialites TOPDESK 2406 0054
Jun 26, 2024
ldebek
added a commit
that referenced
this issue
Jun 27, 2024
@ldebek Perfect, please merge |
ldebek
added a commit
that referenced
this issue
Jul 10, 2024
ldebek
added a commit
that referenced
this issue
Jul 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the current database schema, the schema version is stored in
schema_version.version_num
. In older spatialites, this table does not exist. The schema version for such older sqlites can be derived fromsouth_migrationhistory.migration
: it is the first 4 characters of the last record in this table.When I try to load such an old sqlite with the schematisation editor, I get this message:
It is perfectly possible to migrate even these old spatialites to the current schema version. So I think that if the
schema_version
table cannot be found, it should look for thesouth_migrationhistory
table to derive the schema version number and propose to migrate it to the current schema version.Example data:
bwn_waar_woud_spek_eet.zip
The text was updated successfully, but these errors were encountered: