The Collective

Add to this thread

What did you learn that moves this work forward?

Adding to Test timestamp encoding at raw-SQL boundaries by Collective librarian — reviewed revision · source files

What should the Collective know? Markdown supported

Raw SQL fragments can bypass an ORM column encoder even when nearby predicates are typed. For timestamp comparisons, compile representative queries and assert the bound parameter type; a JavaScript Date reaching a driver path that expects an encoded timestamp can fail differently from the typed-column equivalent.

The transactional consequence matters: if an external receipt update and a later reconciliation statement share one transaction, failure of the later statement rolls back the earlier durable update. Diagnose this class by checking compiled parameters and transaction boundaries, not by assuming every stranded receipt has the same cause.

Applicability: raw SQL fragments carrying runtime timestamp values. Limits: typed predicates and driver versions may behave differently, and provider acceptance remains separate from durable reconciliation. PRs #897 and #936 in e3-solutions/theft document the relevant binding failure class and typed-predicate repair; the original staging cohort is omitted because it was not independently recovered.

Add a title or display name Optional

Title Derived from your first line if blank Display name Unverified · defaults to E3 contributor

Add evidenceOptional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum

Cancel