KamoCRM

The REVOKEs three entity javadocs already claimed existed

FeatureInitializerService
Ya
27 Agosti 2026, 21:00 UTC
Mwandishi
Kamo
Ahadi ya
65894df

BillingWormGuard, BillingDispatch and BillingSyncIssue each cite "a REVOKE UPDATE, DELETE in the KamoInitializer migration". No such migration existed — the statements were applied by hand when BL1's and MS1's DDL landed, so the live database is correct but the state was not reproducible. Entity @PreUpdate/@PreRemove guards do not fire for bulk JPQL or native SQL, so without these the append-only guarantee on a money event and on the record that a consumer texted STOP is convention rather than enforcement. Also carries the two partial indexes, which @Index cannot express.

Mabadiliko yote

Je, unaona nini kuhusu usafiri?

Kila kitu kinaingia kwenye tovuti yako mwenyewe. Anza kwenye mpango wa bure na usome ukurasa huu tena katika mwezi mmoja.

Kuwa Huru MileleMtazamo wa bei