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 declaration of object_uri DB field #453

Merged
merged 1 commit into from
Sep 25, 2020
Merged

Conversation

julien-nc
Copy link
Member

This was making the installation crash on instance where Maps was never installed (all migration scripts running).

Strange that we didn't bump into that earlier. Anyway, old migration scripts run fine on fresh install now.

object_uri column is always affected when inserting/updating maps_address_geo table anyway.

@julien-nc julien-nc added the bug label Sep 25, 2020
@julien-nc julien-nc requested a review from tacruc September 25, 2020 13:38
@julien-nc julien-nc merged commit 70ad2ac into master Sep 25, 2020
@julien-nc julien-nc deleted the fix-migration-object_uri branch September 25, 2020 14:47
@aszlig
Copy link

aszlig commented Oct 10, 2020

@eneiluj: Do you intend to backport this to the Nextcloud 19 release as well? Version 19.0.4 has been released and installing maps now results in the same issue.

aszlig added a commit to aszlig/avonc that referenced this pull request Oct 10, 2020
Since Nextcloud 19.0.4.2, database columns that are non-null can no
longer contain a default of empty string.

This also has been addressed upstream[1], but Nextcloud 19 currently
gets maps version 0.1.6, which does not yet contain this fix.

nextcloud/maps#453

Signed-off-by: aszlig <[email protected]>
@tacruc tacruc mentioned this pull request Oct 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants