Validation of dateTime widget against now() fails

[yanokwa]

Software and hardware versions

Collect v2012.2

Problem description

A constraint of . <= now() on a dateTime widget doesn't constrain when I enter today's date plus an hour later than now. Putting a day later than now works. It would seems only the date is being checked.

In my debugging, when I output the dateTime value in a note, it only shows the date. Using the jump button shows me both date and time. The XML that is persisted shows <rdt_start_time>2021-06-15T01:33:00.000-07:00</rdt_start_time>.

datetime.xlsx is the form I used.

Other information

Enketo shows the datetime, but also seems to check the constraint against only the date.

[lognaturel]

For now I'd consider comparing the date and time separately using date/time functions. You'd need to experiment to figure out the best way to do this -- there's a lot of weirdness in the date/time world.

[lognaturel]

decimal-date-time(.) <= decimal-date-time(now()) does work. I think this is related to the broader theme of "type coercion for date/time/datetime is buggy and/or unexpected". At some point we probably need to review the spec and see what kind of coercion is supposed to happen in an expression like . <= now().