-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Error 1305: FUNCTION gitea.strftime does not exist #5480
Comments
Hmm... Could you check whether this still happens? |
¿which database engine are you using? if I use postgresql my error is this one: |
rebuilt with latest docker image, now it seems to be fixed |
@mnieto156 - I think your problem was Gitea was speaking sqlite dialect to postgres - not sure why. It might have been a configuration issue or an issue with the way it was built. @haytoo1 's problem seems to imply that the strftime function hadn't been compiled into the embedded sqlite - which is probably an issue with the build - so a simple redownload the image and retry might solve the issue and if it's still there after a redownload when Gitea was supposed to have been rebuilt - then it says that there is a consistent problem with the docker build process rather than an intermittent one that might have had something to do with the change of go version that also affected drone's continuous build earlier last week. |
Yeah, thanks, probably my issue was in my config, i've tried a fresh install + docker restart and now it works as expected |
Hi, I have the same problem. I use MySQL instead of sqlite. No bugs in sqlite installation. |
@jnlin have you restarted gitea? |
After restart gitea, it works! Thank you @lunny |
Ah. @lunny - is it that you can change the database backend but the dialect won't change with it until a restart? |
If you changed |
One perennial issue is users running the install page, changing the database dialect and then suffering with issues This PR simply resets all of the database.Use flags on initDBConfig. This should prevent this issue from occuring. Fix go-gitea#13788 Fix go-gitea#5480 Signed-off-by: Andrew Thornton <art27@cantab.net>
One perennial issue is users running the install page, changing the database dialect and then suffering with issues This PR simply resets all of the database.Use flags on initDBConfig. This should prevent this issue from occuring. Fix #13788 Fix #5480 Signed-off-by: Andrew Thornton <art27@cantab.net> Co-authored-by: techknowlogick <techknowlogick@gitea.io>
…3796) Backport go-gitea#13796 One perennial issue is users running the install page, changing the database dialect and then suffering with issues This PR simply resets all of the database.Use flags on initDBConfig. This should prevent this issue from occuring. Fix go-gitea#13788 Fix go-gitea#5480 Signed-off-by: Andrew Thornton <art27@cantab.net> Co-authored-by: techknowlogick <techknowlogick@gitea.io>
…13811) Backport #13796 One perennial issue is users running the install page, changing the database dialect and then suffering with issues This PR simply resets all of the database.Use flags on initDBConfig. This should prevent this issue from occuring. Fix #13788 Fix #5480 Signed-off-by: Andrew Thornton <art27@cantab.net> Co-authored-by: techknowlogick <techknowlogick@gitea.io> Co-authored-by: techknowlogick <techknowlogick@gitea.io>
docker use
gitea/gitea:latest
visit
/api/v1/users/haytoo/heatmap
error message:
The text was updated successfully, but these errors were encountered: