database issue after updating #1086

@daviian commented on GitHub (Sep 21, 2017):

Unfortunately introduced with https://github.com/go-gitea/gitea/pull/2560

@lafriks PR https://github.com/go-gitea/gitea/pull/2451 dropped column can_push

@daviian commented on GitHub (Sep 21, 2017): Unfortunately introduced with https://github.com/go-gitea/gitea/pull/2560 @lafriks PR https://github.com/go-gitea/gitea/pull/2451 dropped column `can_push`

GiteaMirror commented

@lafriks commented on GitHub (Sep 21, 2017):

Oh, I thought it did not drop column. I will fix my migration just then to add it back

@lafriks commented on GitHub (Sep 21, 2017): Oh, I thought it did not drop column. I will fix my migration just then to add it back

GiteaMirror commented

@AntouanK commented on GitHub (Sep 21, 2017):

So how can I fix it?

@AntouanK commented on GitHub (Sep 21, 2017): So how can I fix it?

GiteaMirror commented

@daviian commented on GitHub (Sep 21, 2017):

@AntouanK @lafriks said he will change his migration to fix this.

As you updated to current master, I guess it isn't a productive system?

@daviian commented on GitHub (Sep 21, 2017): @AntouanK @lafriks said he will change his migration to fix this. As you updated to current master, I guess it isn't a productive system?

GiteaMirror commented

2025-11-02 03:47:50 -06:00

@AntouanK commented on GitHub (Sep 22, 2017):

It's a server at home for my personal projects. But it's blocking all my repos now!
Should I revert to an older docker image manually?

@AntouanK commented on GitHub (Sep 22, 2017): It's a server at home for my personal projects. But it's blocking all my repos now! Should I revert to an older docker image manually?

GiteaMirror commented

@ghost commented on GitHub (Sep 22, 2017):

I don't think that reverting to an older docker image will fix your issue. The can_push column in the protected_branch table has been deleted. I recreated the column in the database and now I have gitea running again with the latest docker image.

@ghost commented on GitHub (Sep 22, 2017): I don't think that reverting to an older docker image will fix your issue. The can_push column in the protected_branch table has been deleted. I recreated the column in the database and now I have gitea running again with the latest docker image.

GiteaMirror commented

2025-11-02 03:47:50 -06:00

@AntouanK commented on GitHub (Sep 22, 2017):

I just pulled the latest, and I still get those lines. ( and the web interface is not working )

gitea_1     | 2017/09/22 08:26:21 [T] Custom path: /data/gitea
gitea_1     | 2017/09/22 08:26:21 [T] Log path: /data/gitea/log
postgres_1  | ERROR:  column "can_push" of relation "protected_branch" does not exist at character 31
postgres_1  | STATEMENT:  UPDATE "protected_branch" SET "can_push" = $1, "updated_unix" = $2

@AntouanK commented on GitHub (Sep 22, 2017): I just pulled the latest, and I still get those lines. ( and the web interface is not working ) ``` gitea_1 | 2017/09/22 08:26:21 [T] Custom path: /data/gitea gitea_1 | 2017/09/22 08:26:21 [T] Log path: /data/gitea/log postgres_1 | ERROR: column "can_push" of relation "protected_branch" does not exist at character 31 postgres_1 | STATEMENT: UPDATE "protected_branch" SET "can_push" = $1, "updated_unix" = $2 ```

GiteaMirror commented

2025-11-02 03:47:50 -06:00

@daviian commented on GitHub (Sep 22, 2017):

Like @nellonican said you have to create the can_push column manually afterwards as a temporary fix

@daviian commented on GitHub (Sep 22, 2017): Like @nellonican said you have to create the `can_push` column manually afterwards as a temporary fix

GiteaMirror commented

@ghost commented on GitHub (Sep 22, 2017):

@AntouanK What I did was:

Log in to my postgres database and give the following commands:

gitea-# \c gitea
gitea-# alter table protected_branch add column "can_push" boolean;
gitea-# \q

After that i had to do a docker-compose down and docker-compose up -d

@ghost commented on GitHub (Sep 22, 2017): @AntouanK What I did was: Log in to my postgres database and give the following commands: ```bash gitea-# \c gitea gitea-# alter table protected_branch add column "can_push" boolean; gitea-# \q ``` After that i had to do a `docker-compose down` and `docker-compose up -d`

GiteaMirror commented

@daviian commented on GitHub (Sep 22, 2017):

@nellonican @AntouanK You should set the column to NOT NULL DEFAULT false as well

@daviian commented on GitHub (Sep 22, 2017): @nellonican @AntouanK You should set the column to `NOT NULL DEFAULT false` as well

GiteaMirror commented

@ghost commented on GitHub (Sep 22, 2017):

@daviian Thx. Will do.

@ghost commented on GitHub (Sep 22, 2017): @daviian Thx. Will do.

GiteaMirror commented

@AntouanK commented on GitHub (Sep 22, 2017):

I never used postgres, can you tell me how to log in?
I guess I can do docker exec on the running postgres container somehow to run those commands?

@AntouanK commented on GitHub (Sep 22, 2017): I never used postgres, can you tell me how to log in? I guess I can do `docker exec` on the running postgres container somehow to run those commands?

GiteaMirror commented

@ghost commented on GitHub (Sep 22, 2017):

@AntouanK

docker run -it --rm --link gitea_db_1:postgres postgres:alpine psql -postgres -U postgres

The gitea_db_1 part should be the name of your docker container.

@ghost commented on GitHub (Sep 22, 2017): @AntouanK ```bash docker run -it --rm --link gitea_db_1:postgres postgres:alpine psql -postgres -U postgres ``` The `gitea_db_1` part should be the name of your docker container.

GiteaMirror commented

@AntouanK commented on GitHub (Sep 22, 2017):

That didn't work for me.
Here's how I did it.

docker exec -it gitea_postgres_1 /bin/bash to get access to the postgres container.
psql --username="dbuser" -d "giteadb" to open that interactive shell.
then run \c giteadb and alter table protected_branch add column "can_push" boolean;

seems to be working now, thanks.

@AntouanK commented on GitHub (Sep 22, 2017): That didn't work for me. Here's how I did it. `docker exec -it gitea_postgres_1 /bin/bash` to get access to the postgres container. `psql --username="dbuser" -d "giteadb"` to open that interactive shell. then run `\c giteadb` and `alter table protected_branch add column "can_push" boolean;` seems to be working now, thanks.

GiteaMirror commented

@ghost commented on GitHub (Sep 22, 2017):

@AntouanK, as @daviian mentioned you should also do:

alter table protected_branch alter column "can_push" set DEFAULT false;
alter table protected_branch alter column "can_push" set NOT NULL;

@ghost commented on GitHub (Sep 22, 2017): @AntouanK, as @daviian mentioned you should also do: ```bash alter table protected_branch alter column "can_push" set DEFAULT false; alter table protected_branch alter column "can_push" set NOT NULL; ```

GiteaMirror commented

@ToeiRei commented on GitHub (Sep 22, 2017):

Same problem with my environment here (official docker image on MySQL) - thanks for the hint

@ToeiRei commented on GitHub (Sep 22, 2017): Same problem with my environment here (official docker image on MySQL) - thanks for the hint

GiteaMirror commented

@lunny commented on GitHub (Sep 22, 2017):

@lafriks I think this needs a PR to fix.

@lunny commented on GitHub (Sep 22, 2017): @lafriks I think this needs a PR to fix.

GiteaMirror commented