Skip to content

Invalid char in SQL query #2369

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.

Sign up for GitHub

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

Jump to bottom
Closed
CommanderRoot opened this issue Aug 23, 2017 · 3 comments
Closed

Invalid char in SQL query #2369

CommanderRoot opened this issue Aug 23, 2017 · 3 comments
Labels
type/bug
Milestone
1.3.0

Comments

@CommanderRoot
Copy link
Contributor

gitea/models/repo_list.go

Line 158 in 64b7068

searcherReposCond = searcherReposCond.Or(builder.Expr(`id IN (SELECT repo_id FROM "access" WHERE access.user_id = ? AND owner_id != ?)`,

"access" is not valid in a sql query, it should be `access` instead. This error causes 500 Internal Server errors:

grafik
@lunny
Copy link
Member

lunny commented Aug 23, 2017

fixed by #2361

@lunny lunny closed this as completed Aug 23, 2017
@lunny lunny added the issue/duplicate The issue has already been reported. label Aug 23, 2017
@daviian
Copy link
Member

daviian commented Aug 23, 2017 •
edited
Loading

@lunny I don't think it is fixed. The file models/repo_list.go mentioned here is different then models/action.go from #2361 .

@lunny
Copy link
Member

lunny commented Aug 24, 2017

#2367 will fix this.

@lunny lunny reopened this Aug 24, 2017
@lunny lunny added type/bug and removed issue/duplicate The issue has already been reported. labels Aug 24, 2017
@lunny lunny added this to the 1.3.0 milestone Aug 24, 2017
@lunny lunny mentioned this issue Aug 24, 2017
Merged
@lunny lunny closed this as completed Aug 25, 2017
@go-gitea go-gitea locked and limited conversation to collaborators Nov 23, 2020
6543 pushed a commit to 6543-forks/gitea that referenced this issue Feb 26, 2024
@Gusted
[TRANSLATION] Clarify the description of SSH Keys
553979a 
- Clarify in the description shown in the "Manage SSH Keys" section,
that verified SSH keys can be used as verification for Git commits that
were signed with SSH keys.
- Resolves go-gitea#2369
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
type/bug
Projects
None yet
Milestone
1.3.0
Development

No branches or pull requests
3 participants
@lunny @CommanderRoot @daviian