.Net MEVD: Reexamine PostgreSQL timestamp mapping #10641
Labels
memory connector
memory
msft.ext.vectordata
Related to Microsoft.Extensions.VectorData
.NET
Issue or Pull requests regarding .NET code
The PostgreSQL connector currently maps DateTime to the
timestamp without time zone
type, and DateTimeOffset to thetimestamp with time zone
(link).First, Npgsql itself maps DateTime to
timestamp without time zone
only for DateTime with Kind=Unspecified or Local, and totimestamp with time zone
for Kind=Utc (note thattimestamp with time zone
simply represents a UTC timestamp in PG, just like DateTime with Kind=Utc).Second, Npgsql does not support DateTimeOffset with offsets that aren't zero, since there isn't any PostgreSQL type that actually stores an offset in the database (again,
timestamp with time zone
only stores a timestamp that's meant to represent a UTC timestamp by convention). We should make sure the MEVD connector throws properly for non-zero-offset DateTimeOffsets etc.The text was updated successfully, but these errors were encountered: