Scan hr.careers, and drop the frozen work-location CHECK

FeatureInitializerService
Ya
3 Septemba 2026, 22:01 UTC
Mwandishi
Kamo
Ahadi ya
6c4be99

Two changes, both required before the careers entities can reach the database. The @EnableJpaRepositories list is an explicit array while @EntityScan is wildcard, so leaving com.kamo.z.shared.hr.careers out of it aborts the context, NO runner executes, and the run still reports BUILD SUCCESS having applied nothing. That is the failure this line exists to avoid, and it is silent. **************** gains **************** TeamMember.location is @Enumerated(ORDINAL), so Hibernate froze a CHECK (0..2) when WorkLocationType had three values. FLEXIBLE was appended for the /hr/careers Arrangement field — appending relabels no stored row, but the frozen range refuses the new one, and ddl-auto never widens an existing check. Without the drop, setting a team member's work arrangement to Flexible fails with a 23514 naming a constraint nobody has heard of.

Mabadiliko yote

Je, unaona nini kuhusu usafiri?

Kila moja ya hizi updates ardhi katika nafasi yako ya kazi moja kwa moja. Kuanza bure na kuangalia kukua wiki baada ya wiki.

Kuwa Huru MileleMtazamo wa bei