Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Sorting bug #1843

Closed
Fajfa opened this issue Jul 1, 2024 · 0 comments · Fixed by #1844
Closed

Sorting bug #1843

Fajfa opened this issue Jul 1, 2024 · 0 comments · Fixed by #1844
Assignees
@KinyaElGrande
Labels
backend Backend server changes (GO) bug Something isn't working
Milestone
2023.9.8

Comments

@Fajfa
Copy link
Member

Fajfa commented Jul 1, 2024 •
edited by KinyaElGrande
Loading

Currently, Corteza supports time precision only up to the second mark but saves the timestamp field up to the milliseconds mark (Postgres). This limitation causes a sorting issue when sorting fields with timestamps such as created_at, especially when multiple records have the same timestamp up to the second mark but differ by milliseconds.

This inconsistency affects in pagination and record list count on sort(ASC/DESC).
@Fajfa Fajfa added bug Something isn't working backend Backend server changes (GO) labels Jul 1, 2024
@KinyaElGrande KinyaElGrande mentioned this issue Jul 1, 2024
Merged
@Fajfa Fajfa added this to the 2023.9.8 milestone Jul 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@KinyaElGrande KinyaElGrande

Labels
backend Backend server changes (GO) bug Something isn't working
Projects
None yet
Milestone
2023.9.8
Development

Successfully merging a pull request may close this issue.

Fix Postgres timestamp fields sort inconsistencies cortezaproject/corteza
2 participants
@Fajfa @KinyaElGrande