github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 10:39:38 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Mssql dump import #3931

New Issue
Closed
opened 2025-11-02 05:31:00 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 05:31:00 -06:00
Owner
Copy Link

Originally created by @LukeMauldin on GitHub (Sep 10, 2019).

  • Gitea version (or commit ref): 1.9.3
  • Git version: 2.18
  • Operating system: Windows
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • [x ] Not relevant
  • Log gist:

Description

Current using sqlite as gitea database and want to transition to mssql. Ran ‘gitea dump —database mssql’ but encountered errors when trying to import .sql file.
The problem is that is .sql file uses the literal values of “true” and “false” for Boolean columns. Mssql requires the use of 1 and 0 for Boolean columns.

Originally created by @LukeMauldin on GitHub (Sep 10, 2019). - Gitea version (or commit ref): 1.9.3 - Git version: 2.18 - Operating system: Windows - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [x] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x ] Not relevant - Log gist: ## Description Current using sqlite as gitea database and want to transition to mssql. Ran ‘gitea dump —database mssql’ but encountered errors when trying to import .sql file. The problem is that is .sql file uses the literal values of “true” and “false” for Boolean columns. Mssql requires the use of 1 and 0 for Boolean columns.
GiteaMirror added the status/blockedtype/upstream labels 2025-11-02 05:31:00 -06:00
GiteaMirror commented 2025-11-02 05:31:01 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Sep 11, 2019):

Would you be able to file an upstream bug report for this? We use https://github.com/go-xorm/xorm for database operations.

@techknowlogick commented on GitHub (Sep 11, 2019): Would you be able to file an upstream bug report for this? We use https://github.com/go-xorm/xorm for database operations.
GiteaMirror commented 2025-11-02 05:31:01 -06:00
Author
Owner
Copy Link

@LukeMauldin commented on GitHub (Sep 17, 2019):

Created issue https://github.com/go-xorm/xorm/issues/1426

@LukeMauldin commented on GitHub (Sep 17, 2019): Created issue https://github.com/go-xorm/xorm/issues/1426
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 status/blocked type/upstream
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#3931
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?