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

Migration: Make migration script tolerant of pre-existing indexes #1428

Closed
sbrl opened this issue Apr 1, 2017 · 8 comments

Comments

4 participants
@sbrl
Copy link

commented Apr 1, 2017

As per the conversation on gitter, the migration script should not error out if the index IDX_repo_unit_S or IDX_repo_unit_created_unix already exists. Here's an error I get during the migration process:

2017/04/01 11:31:11 [...itea/routers/init.go:54 GlobalInit()] [E] Failed to initialize ORM engine: migrate: do migrate: CreateIndexes RepoUnit: index IDX_repo_unit_S already exists

Gogs version: 0.10.1.0228

@sbrl sbrl changed the title Migration: Make migration script tolerant of `IDX_repo_unit_S` already existing Migration: Make migration script tolerant of IDX_repo_unit_S already existing Apr 1, 2017

@sbrl sbrl changed the title Migration: Make migration script tolerant of IDX_repo_unit_S already existing Migration: Make migration script tolerant of indexes already existing Apr 1, 2017

@strk

This comment has been minimized.

Copy link
Member

commented Apr 1, 2017

@lunny is there any way to check if an index exist via XORM ?

@tboerger

This comment has been minimized.

Copy link
Member

commented Apr 1, 2017

I think this will be fixed with 1.1.1

@strk

This comment has been minimized.

Copy link
Member

commented Apr 1, 2017

@tboerger you mean it's already fixed in 1.1 branch or do you know of a work in progress ? In either case, do you have links ?

@sbrl

This comment has been minimized.

Copy link
Author

commented Apr 1, 2017

I'm using GItea 1.1.0, so I don't think it's fixed in the 1.1.x branch.

@strk

This comment has been minimized.

Copy link
Member

commented Apr 1, 2017

release/v1.1 branch is 9 commits ahead of 1.1.0

@sbrl

This comment has been minimized.

Copy link
Author

commented Apr 1, 2017

@lunny What's this a duplicate of?

@sbrl sbrl changed the title Migration: Make migration script tolerant of indexes already existing Migration: Make migration script tolerant of pre-existing indexes Apr 1, 2017

@stale

This comment has been minimized.

Copy link

commented Feb 16, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale stale bot added the stale label Feb 16, 2019

@stale

This comment has been minimized.

Copy link

commented Mar 2, 2019

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale stale bot closed this Mar 2, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.