-
-
Notifications
You must be signed in to change notification settings - Fork 366
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.
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
[FEATURE REQUEST] Increase resolution of ocurred_at
in Activities
#1061
Comments
Is the timestamp in the correct order and with enough resolution in the db, or does this requires to change the db structure? |
It seems to be a timestamp, so it should have enough resolucion. So maybe it's related to the method used to save the date: But I'm not 100% sure if what I'm seeing is the field having just resolution up to one second or what... I don't currently have a phpmyadmin to do an |
Sounds like a race condition... Sprunje will sort by one column at a time by design, sorting by |
I don't understand what you mean by race condition in this context. But you're right that sorting by the |
Well, technically it's not a race condition... It's more that the two events happens at the same time and the system (db) is not precise enough to catch it. Note sorting by |
Yes, you're totally right. Would you accept a PR with this change or is it better to do it on my own project? |
PR could be looked at. |
There you have it: #1062 |
It would be nice to have more time resolution (timestamp?) for the Activities:
Right now I'm loging a user in and redirecting it to a page, so there are two events that are registered at the same second in the database. When I check what actions a user has made, I see this:
So the events are in reverse order. If table had more resolution, the
order_by
would solve this.The text was updated successfully, but these errors were encountered: