Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Add default board to new projects, remove uncategorized pseudo-board #29874
Add default board to new projects, remove uncategorized pseudo-board #29874
Changes from all commits
efaa6ce
069687c
b82fdbd
5c49766
53aa0da
1569910
088b715
fc9846b
8660d84
98468df
7267f70
0093855
d326913
2d5c14d
d3a477a
d8781f5
2e25dd5
6f7cb7a
cbe3946
e6e5f3b
5cc2f6e
974a43e
7a5ab60
0b8fb69
a3b861d
42bd419
add886b
5541da4
8ea1715
289cc90
89c1851
f8b35c8
b12a30a
7556836
c0cf2fc
a6fcd20
5405384
4e83bdb
e2190f6
efea1c9
5f69ecc
3e330e8
aa06c97
a3b5aa0
3ad1aa1
a2baeff
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry but this migration seems broken ....
If the "SELECT" results are stable and never change, this
for
loop is right.BUT, by each
SELECT
and for-loop, the "project boards" are changed. The nextSELECT
, it should still process the first page results, but not skipstart
.For example: 150 projects.
SELECT
gets 1-50 projects and updates them.SELECT
gets "the second page" from "51-150", then it gets 101-150 projects.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will send a PR to fix it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#30153
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lunny I believe I still have an issue with this migration. It says: "Ensure every project has exactly one default column". It tries to do some SQL queriy on the
project
andproject_board
tables. Migration seems to fail with error:pq: invalid input syntax for type bigint: "true"
. Help?? I'm stuck on migration. My docker container keeps restating in a loop now. This happens after I updated to v1.22. On version 1.21 everything worked fine.I'm using Docker
gitea/gitea:latest-rootless
image with PostgreSQL v14.When I currently dump the project & project_board schema, it looks like this (hope this helps):
Project table:
Project board table: