Populate a new number before persisting it, not after

FixVOIPService
Shipped
September 6, 2026 at 9:34 PM UTC
Author
Kamo
Commit
9c26f11

save() built an empty OrgPhoneNumber, persisted it, and then filled in E164 and PHONE_CANON — both NOT NULL. It works today because the UUID generator needs no database round trip, so Hibernate defers the insert to flush and sees the final values. That is one eager flush away from inserting a row with two null NOT NULL columns, and nothing in between would say so. Also drops a stray condition that only wrote AUTO_ANSWER's reason when calling was already set up. The flag is false either way, so the explanation should be there either way — a capability that is false with no reason is exactly the silent gap CapabilityLimit exists to close.

All changes

Like what you see shipping?

Every one of these updates lands in your workspace automatically. Start free and watch it grow week after week.

Start Free ForeverView Pricing