github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-22 14:34:54 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

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

New Issue
Closed
opened 2025-11-02 03:29:38 -06:00 by GiteaMirror · 8 comments
GiteaMirror commented 2025-11-02 03:29:38 -06:00
Owner
Copy Link

Originally created by @sbrl on GitHub (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

Originally created by @sbrl on GitHub (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
GiteaMirror added the issue/staleissue/duplicate labels 2025-11-02 03:29:38 -06:00
GiteaMirror commented 2025-11-02 03:29:39 -06:00
Author
Owner
Copy Link

@strk commented on GitHub (Apr 1, 2017):

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

@strk commented on GitHub (Apr 1, 2017): @lunny is there any way to check if an index exist via XORM ?
GiteaMirror commented 2025-11-02 03:29:39 -06:00
Author
Owner
Copy Link

@tboerger commented on GitHub (Apr 1, 2017):

I think this will be fixed with 1.1.1

@tboerger commented on GitHub (Apr 1, 2017): I think this will be fixed with 1.1.1
GiteaMirror commented 2025-11-02 03:29:39 -06:00
Author
Owner
Copy Link

@strk commented on GitHub (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 ?

@strk commented on GitHub (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 ?
GiteaMirror commented 2025-11-02 03:29:39 -06:00
Author
Owner
Copy Link

@sbrl commented on GitHub (Apr 1, 2017):

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

@sbrl commented on GitHub (Apr 1, 2017): I'm using GItea 1.1.0, so I don't think it's fixed in the 1.1.x branch.
GiteaMirror commented 2025-11-02 03:29:39 -06:00
Author
Owner
Copy Link

@strk commented on GitHub (Apr 1, 2017):

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

@strk commented on GitHub (Apr 1, 2017): `release/v1.1` branch is 9 commits ahead of `1.1.0`
GiteaMirror commented 2025-11-02 03:29:39 -06:00
Author
Owner
Copy Link

@sbrl commented on GitHub (Apr 1, 2017):

@lunny What's this a duplicate of?

@sbrl commented on GitHub (Apr 1, 2017): @lunny What's this a duplicate of?
GiteaMirror commented 2025-11-02 03:29:40 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (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[bot] commented on GitHub (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.
GiteaMirror commented 2025-11-02 03:29:40 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Mar 2, 2019):

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

@stale[bot] commented on GitHub (Mar 2, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/duplicate issue/stale
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#602
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?