You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by tcroes April 10, 2024
We recently upgraded from 0.11.34 to 0.11.91 and then to 0.12.11 (in the same evening - in the event timing is an issue). We also use an external LDAP authentication source. We're using mysql.
We are seeing a 500 error when trying to set the LDAP authentication method as default:
Error 1054: Unknown column 'is_default' in 'field list'
We see the same error if we try to add a new LDAP auth method.
Could we have missed a set of necessary database migration changes?
The text was updated successfully, but these errors were encountered:
... and soon you will be upgrading to 0.13, hopefully :)
Anyway, I have no idea when the database was changed, and why the automatic procedure failed, since I'm just a humble user with little to zero experience in hacking the complex Gogs code.
Looking at the Gogs source code documentation for developers, it does indeed seem that table login_source has a column is_default— and I can confirm it on my own installation (which, however, has already been upgraded to 0.13), although phpMyAdmin reports it as a tinyint(1). It's nullable and the default value is 0.
So maybe all you need to do is to manually add that column with the specified parameters and see what happens?... note that adding columns should be pretty much harmless, just wasting a bit of space on the database. It's missing columns that's dangerous!
Discussed in #7723
Originally posted by tcroes April 10, 2024
We recently upgraded from 0.11.34 to 0.11.91 and then to 0.12.11 (in the same evening - in the event timing is an issue). We also use an external LDAP authentication source. We're using mysql.
We are seeing a 500 error when trying to set the LDAP authentication method as default:
Error 1054: Unknown column 'is_default' in 'field list'
We see the same error if we try to add a new LDAP auth method.
Could we have missed a set of necessary database migration changes?
The text was updated successfully, but these errors were encountered: