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

Proposal: Drop integrated tidb support #1796

New Issue
Closed
opened 2025-11-02 04:13:28 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2025-11-02 04:13:28 -06:00
Owner
Copy Link

Originally created by @sapk on GitHub (May 18, 2018).

TiDB since v2 seems to drop the integrated database model and shift to provide a scalable/distributed/mysql compatible independant database server.
So I propose to drop support for the old version that seems to not be use and we haven't provided test or binary for it. We should still be compatible since TiDB is compatible with mysql.

I might be misleading so this PR is to find out if someone use it or if everyone is ok with this proposal.

Originally created by @sapk on GitHub (May 18, 2018). TiDB since v2 seems to drop the integrated database model and shift to provide a scalable/distributed/mysql compatible independant database server. So I propose to drop support for the old version that seems to not be use and we haven't provided test or binary for it. We should still be compatible since TiDB is compatible with mysql. I might be misleading so this PR is to find out if someone use it or if everyone is ok with this proposal.
GiteaMirror added the type/proposal label 2025-11-02 04:13:28 -06:00
GiteaMirror commented 2025-11-02 04:13:29 -06:00
Author
Owner
Copy Link

@sapk commented on GitHub (May 18, 2018):

I had some changes in /vendor kept from when trying to update to last v1 version that was failing.
@sapk commented on GitHub (May 18, 2018): ~~~And it seems that gitea doesn't build with tidb tags :~~~ I had some changes in /vendor kept from when trying to update to last v1 version that was failing.
GiteaMirror commented 2025-11-02 04:13:29 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (May 19, 2018):

Since we could use xgo to cross-compile sqlite. I think remove embed tidb support is acceptable.

@lunny commented on GitHub (May 19, 2018): Since we could use xgo to cross-compile sqlite. I think remove embed tidb support is acceptable.
GiteaMirror commented 2025-11-02 04:13:29 -06:00
Author
Owner
Copy Link

@sapk commented on GitHub (May 19, 2018):

PR ready as this is easy (#3993) but before I think we should wait if anyone complain.

@sapk commented on GitHub (May 19, 2018): PR ready as this is easy (#3993) but before I think we should wait if anyone complain.
GiteaMirror commented 2025-11-02 04:13:30 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (May 22, 2018):

What if we announce that we are going to do this in the 1.5.0 release blog post, and then merge it into master right after 1.5.0 is released that way it will be in 1.6.0

@techknowlogick commented on GitHub (May 22, 2018): What if we announce that we are going to do this in the 1.5.0 release blog post, and then merge it into master right after 1.5.0 is released that way it will be in 1.6.0
GiteaMirror commented 2025-11-02 04:13:30 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Jul 4, 2018):

I've added the note about this to the upcoming 1.5.0 blog post, and PR has been merged so I will close this ticket.

@techknowlogick commented on GitHub (Jul 4, 2018): I've added the note about this to the upcoming 1.5.0 blog post, and PR has been merged so I will close this ticket.
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/proposal
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#1796
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?