fix(fusion_clock): enforce NFC card-UID uniqueness via declarative UniqueIndex
Odoo 19 silently ignores the legacy `_sql_constraints` list (repo CLAUDE.md rule 9), so it never created a DB constraint — two employees could be assigned the same x_fclk_nfc_card_uid and the NFC tap's search(limit=1) then picked an arbitrary one. Replace it with a declarative models.UniqueIndex carrying a partial WHERE predicate, so uniqueness is enforced only when a UID is set; employees without a card keep sharing a blank/NULL value. Makes test_nfc_models.TestNfcModels.test_card_uid_is_unique_when_set pass. Verified on entech (DB admin): 0 pre-existing duplicate UIDs, full upgrade + 61/61 fusion_clock tests green, and the unique partial index hr_employee_fclk_nfc_card_uid_unique now exists. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -5,7 +5,7 @@
|
||||
|
||||
{
|
||||
'name': 'Fusion Clock',
|
||||
'version': '19.0.3.12.2',
|
||||
'version': '19.0.3.12.3',
|
||||
'category': 'Human Resources/Attendances',
|
||||
'summary': 'Complete Employee T&A with Geofencing, Shifts, Penalties, Overtime, Kiosk, Dashboard & Payroll Export',
|
||||
'description': """
|
||||
|
||||
Reference in New Issue
Block a user