PostgreSQL and MySQL accepts microsecond #1815
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#1815
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "master"
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?
In PostgreSQL TIMESTAMP type and MySQL DATETIME can treat microsecond resolution, but xorm can't.
This PR makes xorm puts a timestamp value with microsecond.
@ -0,0 +1,109 @@
package dialects
Please add copyright header.
Done :)
I will leave this to wait CI ready.
@lunny
When will the CI be ready?
I'm having trouble with this problem at work.
@skanehira Please force push this PR and CI will run
26caae7854
to9d5c45d331
@lunny I try
push -f
but CI looks like doesn't run@lunny
There some tests is failed.
I think the cause is microsecond was rounded up.
Should xorm truncated it?
c4c9199278
to965ff217e3
@lunny I fixed some tests but CI doesn't works fine.
It looks like CI resources is not enough.
How can I solve this?
https://drone.gitea.com/xorm/xorm/42/1/18
I will test it locally and merge with administrator permissions.
@lunny
Is this inprogress?
@lunny How about this?
#1815 (comment)
Close this PR.
I'll use forked xorm
Pull request closed