Replies: 2 comments
-
This seems very specific to your use case. Some people may appreciate the additional precision. Is this causing some sort of issue for you? Or is it just that you don't want your users seeing a time with so much precision? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hi, it's about this one. |
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
-
Hi, I suggest changing a bit in behavior of generating
currTime
for bothcreated_at
updated_at
fields. They're now just usingtime.Now
without truncate, so the data after marshal to JSON will also contain the unit value less than second, and I think it shouldn't because of inconsistency with result data from DB selecting. The DB data we query via sqlboiler always return the value for date time field as second rounded.Current:
Suggest to change to:
But I'm not sure if there is really valid for other SQL language, my experience is just about mysql, please share. I can make PR as well.
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions