Age | Commit message (Collapse) | Author | Lines |
|
|
|
we cannot do much about backend errors
|
|
|
|
|
|
result: significant performance improvement for stats generation
|
|
journeys
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
that should be sufficient…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
API v0 has occasional performance issues and is not a preferable
maintenance target
|
|
|
|
|
|
|
|
All travelynx and IRIS timestamps are Europe/Berlin. And the DateTime objects
know that they are Europe/Berlin. However, when inserting into a timestamp with
time zone column, Mojo::Pg or one of the backend DBI/DBD libraries does not
respect the time zone. So, UTC+1 or UTC+2 timestamps are treated as UTC+0,
resulting in major mayhem.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
we can't do anything about "trainlink not found", so it really shouldn't be
a warning.
|
|
|
|
|