github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-05-06 02:02:32 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Question: Primary key state location #4727

New Issue
Closed
opened 2025-11-02 06:00:57 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 06:00:57 -06:00
Owner
Copy Link

Originally created by @ghost on GitHub (Jan 26, 2020).

Let's say we have some repositories. Each repository has an ID (1, 2, 3, etc.) If I delete the 3rd repository and create a new repository, it will get the ID 4 instead of 3. It looks like Gitea stores somewhere stores the value, and increments it when a new repository is created, giving the repository the previous value. If I remove the repository the value does not get changed back, which I completely understand why. My question is, where does this value get stored in the database / files?

Originally created by @ghost on GitHub (Jan 26, 2020). Let's say we have some repositories. Each repository has an ID (1, 2, 3, etc.) If I delete the 3rd repository and create a new repository, it will get the ID 4 instead of 3. It looks like Gitea stores somewhere stores the value, and increments it when a new repository is created, giving the repository the previous value. If I remove the repository the value does not get changed back, which I completely understand why. My question is, where does this value get stored in the database / files?
GiteaMirror added the type/question label 2025-11-02 06:00:57 -06:00
GiteaMirror commented 2025-11-02 06:00:58 -06:00
Author
Owner
Copy Link

@davidsvantesson commented on GitHub (Jan 26, 2020):

It is a feature of SQL databases. The repo id is stored in the database and uses auto increment:
https://www.w3schools.com/sql/sql_autoincrement.asp

@davidsvantesson commented on GitHub (Jan 26, 2020): It is a feature of SQL databases. The repo id is stored in the database and uses auto increment: https://www.w3schools.com/sql/sql_autoincrement.asp
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/question
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#4727
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?