Byte strings in postgres aren't 0x... #1906
No reviewers
Labels
No Label
backport/done
backport/v1
blocked
db
oracle
db
sqlserver
duplicate
feature
cache
frontport/done
frontport/main
invalid
kind
breaking
kind
bug
kind
build
kind
dependencies
kind
docs
kind
driver
kind
enhancement
kind
feature
kind
performance
kind
proposal
kind
question
kind
refactor
kind
testing
need
feedback
need
test
proposal:accepted
RaspBerry Pi
regression
skip-changelog
upstream
wip
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: xorm/xorm#1906
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "zeripath/xorm:fix-bytea-representation-in-postgres"
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?
Byte strings in postgres are actually E'\x...' not 0x...
This is part of the follow-up to #1872
Signed-off-by: Andrew Thornton art27@cantab.net
This bug was present prior to #1872 but #1872 has revealed the issue.
Just noted another format value problem reflect.Map needs to be converted to json too.
And I really think that that is it!
Thanks @lunny I think we might now be able to finally have gitea dump do cross-database dumps properly.
~rIpPeR~ on discord has tried this PR on gitea 1.14.x and successfully converted their db from sqlite to postgres without issues.