Repository navigation
Use timestamp column type in example configs - #2502
Merged
Merged
Conversation
joto
approved these changes
Sep 25, 2026
Collaborator
|
Thank you! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
attributesandtrack-changesLua examples are written as though there is no timestamp type in osm2pgsql, but this is now out of date. It is simpler and unambiguous to use the timestamp type and give osm2pgsql the timestamp as a number. It removes the possibility of mistakes one might make when adapting these examples, say, formatting in local time, or leaving out the timezone. The resulting tables are the same, with the exception of that nil times stay as null rather than silently being converted to the current time (which is ~certainly wrong).