Quote from
Gaev on April 5, 2022, 7:56 pm
@pauljonestindall
From your other post ...
I found that the postgresql database would not accept an invalid date.
In my text entry object I can type in an invalid date but when I use dbpSaveEdits, the field would not populate or if the field is already populated, it would not save the change. With no notification. So, I'd rather validate the date at the point of entry.
Good practice no matter what the target DB.
Also, specifying content for date fields gets tricky (if i recall, you have to surround the date with ## characters).
@pauljonestindall
From your other post ...
I found that the postgresql database would not accept an invalid date.
In my text entry object I can type in an invalid date but when I use dbpSaveEdits, the field would not populate or if the field is already populated, it would not save the change. With no notification. So, I'd rather validate the date at the point of entry.
Good practice no matter what the target DB.
Also, specifying content for date fields gets tricky (if i recall, you have to surround the date with ## characters).