It looks like it currently defaults to UNIX time (to be checked), which is not what we want.
AFAICT it should be enough to use as default timestamp the equivalent of "now", and the "closest timestamp" semantics which we already have should take care of the rest (again: to be verified).
Description
Description
Related Objects
Related Objects
- Mentioned In
- R65:cb1e3bb82c99: /revision/origin/: Make the timestamp default to the most recent visit
rDWAPPScb1e3bb82c99: /revision/origin/: Make the timestamp default to the most recent visit - Mentioned Here
- rDSTOb5b8fd06eaf7: sql/swh-func: actually filter swh_visit_find_by_date by origin...
rDSTO48df525f718e: sql/swh-func: in occurrence_get_by: only return data pertaining one visit
Event Timeline
Comment Actions
Related:
- b5b8fd06eaf7492bca1f55f108eede623a8cffad
- 48df525f718eb54e37c9b24548825511515b8028