Temporal And Streaming Procedures
Consumer View
These procedures cover the parts of Nexyron's temporal surface that are exposed as CALL procedures rather than as row-pipeline clauses.
All temporal bounds passed to these procedures are canonical i64 epoch-millisecond integers. Use datetime(...), timestamp(), currenttimestamp(), or stored timestamp properties directly; they all produce the same scalar format. Procedure outputs such as ts, start_ts, and end_ts also use epoch milliseconds.
They matter when you need one of these jobs:
- scan timeline events across the whole graph
- scan timeline events for a selected entity set
- find the latest available temporal timestamp without scanning the whole timeline
- read one temporal property history for one subject
- read one temporal-property rollup for one subject
- aggregate one declared temporal property across all or selected subjects by year, month, week, day, or fixed-width bucket
Procedures
- nexyron.latest_global_temporal_event
- nexyron.global_time_range
- nexyron.global_time_bins
- nexyron.entity_time_range
- nexyron.temporal_history
- nexyron.temporal_rollup
- nexyron.temporal_bucket_aggregate
- nexyron.temporal_bucket_group_aggregate
- nexyron.temporal_geo_dbscan
- nexyron.temporal_geo_dbscan_many
Conceptual Explanation
These procedures sit between normal Cypher querying and Nexyron's time-aware storage helpers.
Use the clause surface when you are shaping rows inside a normal query pipeline. Use these procedures when you need timeline scans or one direct read of a temporal property history/rollup for one known subject.