New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trunk 4156 redesigned #501
Conversation
1. Introduce new care_setting table. 2. Replace existing care_setting varchar to care_setting_id referencing the care_setting table. 3. Make OUTPATIENT as default care_setting for existing orders that do not have a care_setting. 4. Introduce new method in OrderService. This fixes a test and provides a way to retrieve a care setting.
|
||
public static CareSetting OUTPATIENT = new CareSetting(OUT_PATIENT); | ||
private CareSettingType careSettingType = CareSettingType.OUTPATIENT; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think you should be setting a default value here, just leave it null
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
</insert> | ||
</changeSet> | ||
|
||
<changeSet id="201312271825-TRUNK-4156" author="vinay"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You don't need to be dropping this column with liquibase here since it doean't exist in a release openmrs version, just drop it with sql from your local mysql instance. I will fix this as i merge the code
You forgot to change the column names for orders.care_setting and care_setting.care_setting_type in the hbm and test data files, i will fix that as i merge the code too |
Merged the code at 3863412 |
The idea here is to ensure that failing to load a script complains loudly but doesn't break the application.
Hi,
Commit 8dd08a1 is a minor fix with the existing liquibasechangelog (unrelated to the story, but we cannot work without it).
-Vinay