GNU Health - Bugs: bug #46009, Make specialty field required and...
You are not allowed to post comments on this tracker with your current authentication level.
bug #46009: Make specialty field required and cascade in hp_specialty
Submitter: | Marc Murray <marcdm> | ||
Submitted: | Sun 20 Sep 2015 04:32:29 PM UTC | ||
Category: | Programming / Tracebacks | Severity: | 3 - Normal |
Item Group: | None | Status: | None |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Open | Release: | None |
Module: | health | Component: | None |
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follows 1 latest change.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2015-09-20 | marcdm | Attached File | - | ![]() |
Added hp_specialty-001.patch, #34938 |
The specialty field is optional on HealthProfessionalSpecialty. This can lead to accidental records with this value as null. This causes an error in the display and makes all other specialties of this HealthProf show blank.
It also causes the "Specialties by health professional" report to generate an error and come up blank.
To reproduce the error, click the icon to add a specialty for a Health Professional. Then just click Ok without selecting a specialty. Then save the health professional. The same will happen if you select one, then click "New" then Ok.
The patch attached makes both the name and specialty fields required and ondelete='CASCADE'.
It also introduces a constraint that makes name + specialty unique. This is done so the same specialty cannot be selected twice.