V7.0.1 datetime issue

[snailwell (Jason X)]

When creating a new encounter in v7.0.1, this code ensures that for any service date with a ‘pm’ suffix, the time will be formatted correctly, e.g. '17:45:00'. However, if the service date has an ‘am’ suffix, the time will remain unformatted and will be inserted into the database as such, e.g. '2023-05-05 11:00 am'.

This issue is not reproducible on the demo I suspect because the mariadb:10.11 image can handle datetime input such as '2023-05-05 11:00 am'. However, the mysql-xtrabackup:latest image used in the AWS packages (and probably older mariadb versions as well) cannot, and will produce an error like ERROR 1292 (22007): Incorrect datetime value: '2023-05-05 11:00 am' for column 'date' at row 1 upon insert.

This could partially explain these issues:

Date/Time error in rel-700 when using 12 hour format

After re-basing using the newest version of rel-700, I found issues when creating encounters if I am using 12 hour format. Surprisingly I haven’t seen any mention in the forums about this . When I look at the code I see the following: [image] So when we pick a date we get either ‘am’ or ‘pm’ in the time slot… Then when the encounter is saved we get a garbled date: [image] Even when I look at Master I see the same value of ‘true’ for the datepicker_timepicker. [image] Also, looking at …

7.0.0(1): Encounter date field of encounter form not retaining the date

Situation 7.0.0(1): Encounter date field of encounter form not retaining the date. This is happening a lot (easily reproducible). The encounter form does not retain the date information and gets a date of 00/00/00 XX:XX. This becomes obvious when selecting the encounter after creating it, and the tab has a date such as 0-/01/-3. It’s easy to repair by navigating back into the form and editing the date again (picking it from the calendar picker) and saving. It’s a hassle because it happens…

Negative Dates in Creating New Encounter

Hello All, After upgrade to V7.0.1 i have negative encounter dates. Please see image below. [Screen Shot 2022-09-03 at 12.28.40 PM] How can i fix this?

@jesdynf , can you check for this in the AWS mysql-xtrabackup image?
@stephenwaite , can the time formatting code be standardized for all input?

[stephenwaite]

hi @snailwell , does removing the if condition in the code you pointed to solve the issue?

[snailwell (Jason X)]

Yes, without the ‘if’ condition it works for me with both ‘am’ and ‘pm’ for both date of service and onset date when creating a new encounter. Using the current mysql-xtrabackup:latest image as datastore.

[jesdynf (Asher Densmore-Lynn)]

Eeesh. I should sit down and see if I oughta upgrade that version of MySQL in there, but this sounds more like a MySQL/MariaDB conflict that might not help. May just need to ask for a patch.

[stephenwaite]

Have a PR up and will get this fix into the 1st patch.