BigQueryStruct with DateTimeOffset property gets misread by EF as a DateTime causing an exception.

[retroandchill]

As the title says creating a struct like this:

[BigQueryStruct]
public sealed class LastReport
{
    public DateTimeOffset Time { get; set; }

    public long Offset { get; set; }
}

leads to this error:

System.ArgumentException: Object of type 'System.DateTime' cannot be converted to type 'System.DateTimeOffset'.,

It seems like the underlying Dictionary containing the value contains a DateTime instead of DateTimeOffset for the value in question. I'm not sure if this is a config issue or something deeper with the library.

[retroandchill]

I did a bit more digging and it appears it comes out of BigQuery as a DateTime value, so that's the source of the issue.

[retroandchill]

Also found an issue inserting or updating structs, namely that BQ doesn't support using structs as parameters, so insert and update statements need to be fully expanded.

[dovydasm]

Please check the DateTimeOffset fix in https://github.com/Ivy-Interactive/Ivy.EntityFrameworkCore.BigQuery/tree/fix/struct-typemappings

Also, could you please provide the code to reproduce your insert and update issues? We currently generate literal values instead of parameters in INSERT/UPDATE for STRUCT and ARRAY<STRUCT> in order to get around the SDK limitations and it has worked so far with simple tests.