fix: Restore MSSQL and Oracle nanosecond timestamp notes from trunk

Copilot · lukekim · web-flow · commit 2fe576ee7666 · 2026-04-21T18:38:35.000Z
Co-authored-by: lukekim &lt;80174+lukekim@users.noreply.github.com&gt;
diff --git a/website/versioned_docs/version-1.10.x/components/data-connectors/mssql.md b/website/versioned_docs/version-1.10.x/components/data-connectors/mssql.md
@@ -12,6 +12,7 @@ The Microsoft SQL Server Data Connector enables federated/accelerated SQL querie
 
 1. The connector supports SQL Server authentication (SQL Login and Password) only.
 1. Spatial types (`geography`) are not supported, and columns with these types will be ignored.
+1. `DATETIME2` and `DATETIMEOFFSET` columns are mapped to Arrow `Timestamp(Nanosecond)`. Timestamps outside the nanosecond range (approximately years 1677–2262) will silently return `1970-01-01 UTC`. This is an inherent limitation of Arrow's nanosecond timestamp representation.
 
 :::
 
diff --git a/website/versioned_docs/version-1.10.x/components/data-connectors/oracle.md b/website/versioned_docs/version-1.10.x/components/data-connectors/oracle.md
@@ -117,6 +117,7 @@ The table below shows the Oracle data types supported, along with the type mappi
 :::note
 
 - The Oracle `TIMESTAMP WITH LOCAL TIME ZONE` value is retrieved as a UTC time value.
+- `TIMESTAMP`, `TIMESTAMP WITH TIME ZONE`, and `TIMESTAMP WITH LOCAL TIME ZONE` columns with non-zero precision are mapped to `Timestamp(Nanosecond)`. Timestamps outside the nanosecond range (approximately years 1677–2262) will silently return `1970-01-01 UTC`. This is an inherent limitation of Arrow's nanosecond timestamp representation.
 
 :::
 
diff --git a/website/versioned_docs/version-1.11.x/components/data-connectors/mssql.md b/website/versioned_docs/version-1.11.x/components/data-connectors/mssql.md
@@ -12,6 +12,7 @@ The Microsoft SQL Server Data Connector enables federated/accelerated SQL querie
 
 1. The connector supports SQL Server authentication (SQL Login and Password) only.
 1. Spatial types (`geography`) are not supported, and columns with these types will be ignored.
+1. `DATETIME2` and `DATETIMEOFFSET` columns are mapped to Arrow `Timestamp(Nanosecond)`. Timestamps outside the nanosecond range (approximately years 1677–2262) will silently return `1970-01-01 UTC`. This is an inherent limitation of Arrow's nanosecond timestamp representation.
 
 :::
 
diff --git a/website/versioned_docs/version-1.11.x/components/data-connectors/oracle.md b/website/versioned_docs/version-1.11.x/components/data-connectors/oracle.md
@@ -117,6 +117,7 @@ The table below shows the Oracle data types supported, along with the type mappi
 :::note
 
 - The Oracle `TIMESTAMP WITH LOCAL TIME ZONE` value is retrieved as a UTC time value.
+- `TIMESTAMP`, `TIMESTAMP WITH TIME ZONE`, and `TIMESTAMP WITH LOCAL TIME ZONE` columns with non-zero precision are mapped to `Timestamp(Nanosecond)`. Timestamps outside the nanosecond range (approximately years 1677–2262) will silently return `1970-01-01 UTC`. This is an inherent limitation of Arrow's nanosecond timestamp representation.
 
 :::
 
diff --git a/website/versioned_docs/version-1.5.x/components/data-connectors/mssql.md b/website/versioned_docs/version-1.5.x/components/data-connectors/mssql.md
@@ -12,6 +12,7 @@ The Microsoft SQL Server Data Connector enables federated/accelerated SQL querie
 
 1. The connector supports SQL Server authentication (SQL Login and Password) only.
 1. Spatial types (`geography`) are not supported, and columns with these types will be ignored.
+1. `DATETIME2` and `DATETIMEOFFSET` columns are mapped to Arrow `Timestamp(Nanosecond)`. Timestamps outside the nanosecond range (approximately years 1677–2262) will silently return `1970-01-01 UTC`. This is an inherent limitation of Arrow's nanosecond timestamp representation.
 
 :::
 
diff --git a/website/versioned_docs/version-1.5.x/components/data-connectors/oracle.md b/website/versioned_docs/version-1.5.x/components/data-connectors/oracle.md
@@ -117,6 +117,7 @@ The table below shows the Oracle data types supported, along with the type mappi
 :::note
 
 - The Oracle `TIMESTAMP WITH LOCAL TIME ZONE` value is retrieved as a UTC time value.
+- `TIMESTAMP`, `TIMESTAMP WITH TIME ZONE`, and `TIMESTAMP WITH LOCAL TIME ZONE` columns with non-zero precision are mapped to `Timestamp(Nanosecond)`. Timestamps outside the nanosecond range (approximately years 1677–2262) will silently return `1970-01-01 UTC`. This is an inherent limitation of Arrow's nanosecond timestamp representation.
 
 :::
 
diff --git a/website/versioned_docs/version-1.6.x/components/data-connectors/mssql.md b/website/versioned_docs/version-1.6.x/components/data-connectors/mssql.md
@@ -12,6 +12,7 @@ The Microsoft SQL Server Data Connector enables federated/accelerated SQL querie
 
 1. The connector supports SQL Server authentication (SQL Login and Password) only.
 1. Spatial types (`geography`) are not supported, and columns with these types will be ignored.
+1. `DATETIME2` and `DATETIMEOFFSET` columns are mapped to Arrow `Timestamp(Nanosecond)`. Timestamps outside the nanosecond range (approximately years 1677–2262) will silently return `1970-01-01 UTC`. This is an inherent limitation of Arrow's nanosecond timestamp representation.
 
 :::
 
diff --git a/website/versioned_docs/version-1.6.x/components/data-connectors/oracle.md b/website/versioned_docs/version-1.6.x/components/data-connectors/oracle.md
@@ -117,6 +117,7 @@ The table below shows the Oracle data types supported, along with the type mappi
 :::note
 
 - The Oracle `TIMESTAMP WITH LOCAL TIME ZONE` value is retrieved as a UTC time value.
+- `TIMESTAMP`, `TIMESTAMP WITH TIME ZONE`, and `TIMESTAMP WITH LOCAL TIME ZONE` columns with non-zero precision are mapped to `Timestamp(Nanosecond)`. Timestamps outside the nanosecond range (approximately years 1677–2262) will silently return `1970-01-01 UTC`. This is an inherent limitation of Arrow's nanosecond timestamp representation.
 
 :::
 
diff --git a/website/versioned_docs/version-1.7.x/components/data-connectors/mssql.md b/website/versioned_docs/version-1.7.x/components/data-connectors/mssql.md
@@ -12,6 +12,7 @@ The Microsoft SQL Server Data Connector enables federated/accelerated SQL querie
 
 1. The connector supports SQL Server authentication (SQL Login and Password) only.
 1. Spatial types (`geography`) are not supported, and columns with these types will be ignored.
+1. `DATETIME2` and `DATETIMEOFFSET` columns are mapped to Arrow `Timestamp(Nanosecond)`. Timestamps outside the nanosecond range (approximately years 1677–2262) will silently return `1970-01-01 UTC`. This is an inherent limitation of Arrow's nanosecond timestamp representation.
 
 :::
 
diff --git a/website/versioned_docs/version-1.7.x/components/data-connectors/oracle.md b/website/versioned_docs/version-1.7.x/components/data-connectors/oracle.md
@@ -117,6 +117,7 @@ The table below shows the Oracle data types supported, along with the type mappi
 :::note
 
 - The Oracle `TIMESTAMP WITH LOCAL TIME ZONE` value is retrieved as a UTC time value.
+- `TIMESTAMP`, `TIMESTAMP WITH TIME ZONE`, and `TIMESTAMP WITH LOCAL TIME ZONE` columns with non-zero precision are mapped to `Timestamp(Nanosecond)`. Timestamps outside the nanosecond range (approximately years 1677–2262) will silently return `1970-01-01 UTC`. This is an inherent limitation of Arrow's nanosecond timestamp representation.
 
 :::
 
diff --git a/website/versioned_docs/version-1.8.x/components/data-connectors/mssql.md b/website/versioned_docs/version-1.8.x/components/data-connectors/mssql.md
@@ -12,6 +12,7 @@ The Microsoft SQL Server Data Connector enables federated/accelerated SQL querie
 
 1. The connector supports SQL Server authentication (SQL Login and Password) only.
 1. Spatial types (`geography`) are not supported, and columns with these types will be ignored.
+1. `DATETIME2` and `DATETIMEOFFSET` columns are mapped to Arrow `Timestamp(Nanosecond)`. Timestamps outside the nanosecond range (approximately years 1677–2262) will silently return `1970-01-01 UTC`. This is an inherent limitation of Arrow's nanosecond timestamp representation.
 
 :::
 
diff --git a/website/versioned_docs/version-1.8.x/components/data-connectors/oracle.md b/website/versioned_docs/version-1.8.x/components/data-connectors/oracle.md
@@ -117,6 +117,7 @@ The table below shows the Oracle data types supported, along with the type mappi
 :::note
 
 - The Oracle `TIMESTAMP WITH LOCAL TIME ZONE` value is retrieved as a UTC time value.
+- `TIMESTAMP`, `TIMESTAMP WITH TIME ZONE`, and `TIMESTAMP WITH LOCAL TIME ZONE` columns with non-zero precision are mapped to `Timestamp(Nanosecond)`. Timestamps outside the nanosecond range (approximately years 1677–2262) will silently return `1970-01-01 UTC`. This is an inherent limitation of Arrow's nanosecond timestamp representation.
 
 :::
 
diff --git a/website/versioned_docs/version-1.9.x/components/data-connectors/mssql.md b/website/versioned_docs/version-1.9.x/components/data-connectors/mssql.md
@@ -12,6 +12,7 @@ The Microsoft SQL Server Data Connector enables federated/accelerated SQL querie
 
 1. The connector supports SQL Server authentication (SQL Login and Password) only.
 1. Spatial types (`geography`) are not supported, and columns with these types will be ignored.
+1. `DATETIME2` and `DATETIMEOFFSET` columns are mapped to Arrow `Timestamp(Nanosecond)`. Timestamps outside the nanosecond range (approximately years 1677–2262) will silently return `1970-01-01 UTC`. This is an inherent limitation of Arrow's nanosecond timestamp representation.
 
 :::
 
diff --git a/website/versioned_docs/version-1.9.x/components/data-connectors/oracle.md b/website/versioned_docs/version-1.9.x/components/data-connectors/oracle.md
@@ -117,6 +117,7 @@ The table below shows the Oracle data types supported, along with the type mappi
 :::note
 
 - The Oracle `TIMESTAMP WITH LOCAL TIME ZONE` value is retrieved as a UTC time value.
+- `TIMESTAMP`, `TIMESTAMP WITH TIME ZONE`, and `TIMESTAMP WITH LOCAL TIME ZONE` columns with non-zero precision are mapped to `Timestamp(Nanosecond)`. Timestamps outside the nanosecond range (approximately years 1677–2262) will silently return `1970-01-01 UTC`. This is an inherent limitation of Arrow's nanosecond timestamp representation.
 
 :::
 
