- Shipped
- 2 செப்டம்பர், 2026 அன்று 3:12 PM UTC
- Author
- Kamo
- Commit
- c3327a4
A method was inserted between @CreationTimestamp and the dateCreated field it annotates, so the annotation bound to subject() instead. These entities are read by field access, so Hibernate ignored it there and sent DATE_CREATED out null. **************** is NOT NULL with no database default, so every insert was refused: ERROR: null value in column "date_created" of relation "lead_communications" violates not-null constraint The refusal lands inside LeadCommunicationLinker.link, which catches and warns because association is best-effort — so calls, texts, voicemails and e-mails stopped attaching to leads on 2026-08-21 with nothing louder than a WARN to say so, and the Communications card has read zero for every one of them since. CommsTimestampMappingTest pins the mapping for all four comms entities, and names the actual mistake rather than its consequence: an annotation stranded on a method still compiles and still passes every mocked test, and only fails at the database.