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 220 fails against MSSQL 2008R2 SP3 database #20615

Closed
snoopydo opened this issue Aug 2, 2022 · 0 comments · Fixed by #20702
Closed

Migration 220 fails against MSSQL 2008R2 SP3 database #20615

snoopydo opened this issue Aug 2, 2022 · 0 comments · Fixed by #20702
Labels
Milestone

Comments

@snoopydo
Copy link

snoopydo commented Aug 2, 2022

Description

When upgrading to 1.17, the process failed.

Gitea Version

1.17

Can you reproduce the bug on the Gitea demo site?

No

Operating System

Windows 10

How are you running Gitea?

On windows 10 as a service. Using MSSQL 2008R2 SP3 for the database. this is the minimum supported version according to the configuration | databases section of https://docs.gitea.io/en-us/ however CONCAT isn't supported by MSSQL till version 2016 I think.

2022/08/02 14:30:05 cmd/web.go:160:runWeb() [I] PING DATABASE mssql
2022/08/02 14:30:05 ...ations/migrations.go:501:Migrate() [I] Migration[220]: Add container repository property
2022/08/02 14:30:05 routers/common/db.go:33:InitDBEngine() [E] ORM engine initialization attempt #7/10 failed. Error: migrate: migration[220]: Add container repository property failed: mssql: 'CONCAT' is not a recognized built-in function name.
2022/08/02 14:30:05 routers/common/db.go:34:InitDBEngine() [I] Backing off for 3 seconds
2022/08/02 14:30:08 routers/common/db.go:27:InitDBEngine() [I] ORM engine initialization attempt #8/10...

Database

MSSQL

@snoopydo snoopydo changed the title Migration 220 fails against MSSQL database MSSQL Migration 220 fails against MSSQL 2008R2 SP3 database Aug 2, 2022
@wxiaoguang wxiaoguang added this to the 1.17.1 milestone Aug 2, 2022
@go-gitea go-gitea locked and limited conversation to collaborators May 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants