Hi all, Today we found a dangerous bug which is related to the LBF’s. This was found in 500 so I am unsure if this was fixed in 501. I think this is the right place to post this, but here goes:
In modifying an LBF a user created a column called ‘date’. Then, in deleting the column after deciding it wasn’t wanted it deleted the date column in the history_data table. Unfortunately, the date column is used in several queries and it shut down use of OpenEMR.
As a fix I recreated a date column. In my copy on my localhost, date can be NULL. This seems to work. Does anyone see potential issues by keeping the values NULL?
In the LBF’s there should be some data entry validation that 1) prevents the elimination of a column or 2) naming a column after an existing column. mySQL doesn’t allow it, but we shouldn’t even be able to get to the point where mySQL is throwing an error. Maybe we can just make it impossible to delete a column?