Skip to content

Commit 0aa0f55

Browse files
Update content/integrate/redis-data-integration/data-pipelines/transform-examples/formatting-date-and-time-values.md
Co-authored-by: andy-stark-redis <164213578+andy-stark-redis@users.noreply.github.com>
1 parent 60e7113 commit 0aa0f55

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/integrate/redis-data-integration/data-pipelines/transform-examples/formatting-date-and-time-values.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,7 @@ SQL Server supports the following date and time data types:
9292
expression: STRFTIME('%Y-%m-%d %H:%M:%S', event_datetime / 1000, 'unixepoch')
9393
```
9494

95-
- `datetime2` - similar to `datetime` but with higher precision. For `datetime2(0-3)` the representation is the same as for `datetime`. For `datetime2(4-6)` it is the number of microseconds since epoch. and for `datetime2(7)` it is the number of nanoseconds since epoch. You can use the same approach as for `datetime` but you need to divide by 1000, 1000000 or 1000000000 depending on the precision.
95+
- `datetime2` - similar to `datetime` but with higher precision. For `datetime2(0-3)`, the representation is the same as for `datetime`. For `datetime2(4-6)`, it is the number of microseconds since epoch. For `datetime2(7)`, it is the number of nanoseconds since epoch. To convert to another time unit, you can use the same approach as for `datetime` but you need to divide by 1000, 1000000 or 1000000000 depending on the precision.
9696

9797
- `time` - the time of milliseconds since midnight.
9898
```yaml

0 commit comments

Comments
 (0)