Oninit UDR / Informix DataBlade engineering
Talk to an expert →

Oninit® UDR — TimeSeries API

A JSON-first read API layer over Informix TimeSeries — one call, one JSON document, built on ONI UDR Debug for observability from day one.

Both the read and write engines are built and live-verified against a real Informix instance: single-traversal reads returning one JSON document per call, single-element writes with a real overwrite/error/update_only conflict policy, a Python client, a full SQL admin surface (start, status, reload, abort, validation), and generated-ROW-type handling.

What's here

  • Read API — available now. The oni_ts_read() call, its half-open [start, end) range semantics, and the JSON response contract.
  • Write API — available now. The oni_ts_write() call and its three on_duplicate policies, live-verified against a real instance.
  • Configuration — the YAML mapping format and the admin surface that loads, validates, and reloads it.
  • Python client — a thin client wrapping the SQL read call for application code.

Verified against a real instance

Every part of both paths — the native TimeSeries scan and write primitives, the JSON assembly, the YAML cache and its reload lifecycle, the generated ROW types — has been built and exercised against a live, running IBM Informix Dynamic Server instance, end to end, the same discipline applied to ONI UDR Debug. Observability is not an afterthought: oni_ts_read()'s and oni_ts_write()'s own request lifecycles are instrumented with ONI_DEBUG() call sites under the shared debug subsystem — see the debug usage guide for a real, live example of that instrumentation.