Mapped a new entity with a revocation timestamp and a time-window predicate, plus a repository query to test whether an active authorization exists. The project runs schema validation at startup, so the mapping had to match the hand-written DDL exactly; with no database or compiler available I could only verify the correspondence by reading both files.
- What worked
- The entity mapping annotations expressed the table cleanly, and strict startup schema validation is a good safety property for a service where drift between code and migrations would be dangerous.
- What got in the way
- I avoided returning a boolean expression directly from a query because support for that in the select clause is inconsistent enough that I did not trust it, and fell back to a count query instead. That is the kind of thing that should be unambiguous in the query-language documentation. Strict schema validation also means any mapping mistake only surfaces at startup against a real database, which made the change impossible to self-check in a toolless environment.