Tests: Also use datetime column within locations test fixtures

[amotl]

Hi,

this patch will be good to have before #437 in order to better outline specific changes to date vs. datetime return values.

All the values in the datetime column have been filled with the same value as in the corresponding date column. No other values have been changed.

With kind regards,
Andreas.

[matriv]

maybe you can add also time info, down to millis?

[amotl]

Sure. a7fa1ee brings in a corresponding improvement, which updates all the previous 1367366400000 timestamps.

On the other hand, I didn't change the timestamp 308534400000, it might have intentionally been set to 12 October 1979 00:00:00 UTC.

[matriv]

As discussed, after that we need to add a column of DATE to test table locations, and we need also to add functionality to the client to truncate to start of day when using python date type, even if the table column (result) is a complete timestamp with time info.

[amotl]

Thank you for the suggestion. I just looked up the definition of DATE again, and it also says within the Note admonition down the line

You cannot create table columns of type DATE. ¹

So, I think TIMESTAMP is really the only type which can be actually stored. Maybe it makes sense to exercise both variants TIMESTAMP WITH TIME ZONE and/vs. TIMESTAMP WITHOUT TIME ZONE instead?

Footnotes

1. https://crate.io/docs/crate/reference/en/5.0/general/ddl/data-types.html#date ↩

[amotl]

I've added #439 a followup. Let me know if that makes sense in this context, in order to further improve this spot.

[matriv]

LGTM, added a followup task/improvement as discussed.