You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
your client configuration (what repository you use, which database, versions of the parties involved will be helpful too)
database id's of those events (if it's not a problem)
is it a global stream displayed or a specific one
The more details, the better.
This issue is not the matter of sorting events in browser. They're ordered by their primary keys unless specifically asked (not possible in RES::Browser). I'm 99% sure they're ordered the same way in your event_store_events table, but I want to be 100% sure on that, so we can discuss this further.
Below you can find a sample events published with sleep(0.1) in between on Rails 8 app with PostgreSQL 15, RES 2.15.0 and default JSONClient configuration. As you might notice, the timestamps are diminishing as expected.
Hi guys. Do you think it would be possible to also sort by milliseconds in the browser
12:15:45.524 should come after 12:15:45.300 -> which is also the right causality
Thanks
The text was updated successfully, but these errors were encountered: