Replies: 1 comment
-
|
Closing because turned it into an issue |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
When a
:datecol-typeis inflated, alocal-timetimestamp is returned instead of either just the string value of the date or an object representing a date. See here:mito/src/core/dao/column.lisp
Line 79 in c337a17
mito/src/core/dao/column.lisp
Line 86 in c337a17
Note that deflation is fine because it allows for the string value:
mito/src/core/dao/column.lisp
Line 134 in c337a17
I would hope standard behavior for
:datereturns a date, whether as a string or an object, not a different data type.Can we either return a string or at least use a date typed object?
There are a few libraries to deal with dates specifically, since
local-timeonly deals with timestamps. See here: https://github.com/CodyReichert/awesome-cl?tab=readme-ov-file#date-and-timeTwo in particular jumped to mind, both built on top of
local-time:It seems only
periodsis available in quicklisp: https://www.quicklisp.org/beta/releases.htmlI would be happy to make a PR to fix this. I have no horse in choosing whichever library, I would just like for the dates to return a correct data type.
What do you think?
Beta Was this translation helpful? Give feedback.
All reactions