Skip to content

Commit

Permalink
docs: update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
silviustanimir authored and cverhoef committed Nov 13, 2023
1 parent 4205075 commit 79f9b81
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,8 +17,8 @@ vars:
# Date and time formats.
# For SQL Server defined by integers and for Snowflake/Databricks defined by strings.
date_format: 23 # default: SQL Server: 23, Snowflake: 'YYYY-MM-DD', Databricks: 'yyyy-MM-dd'
time_format: 14 # default: SQL Server: 14, Snowflake: 'hh24:mi:ss.ff3', Databricks: 'HH:mm:ss[.SSS]'
datetime_format: 21 # default: SQL Server: 21, Snowflake: 'YYYY-MM-DD hh24:mi:ss.ff3', Databricks: 'yyyy-MM-dd HH:mm:ss[.SSS]'
time_format: 14 # default: SQL Server: 14, Snowflake: 'hh24:mi:ss.ff3', Databricks: 'HH:mm:ss'
datetime_format: 21 # default: SQL Server: 21, Snowflake: 'YYYY-MM-DD hh24:mi:ss.ff3', Databricks: 'yyyy-MM-dd HH:mm:ss'
```

## Contents
Expand Down Expand Up @@ -146,7 +146,7 @@ Usage:
`{{ pm_utils.to_integer('[expression]') }}`

#### to_timestamp ([source](macros/multiple_databases/to_timestamp.sql))
This macro converts a field to a timestamp field.
This macro converts a field to a timestamp field. For Databricks, milliseconds will automatically be parsed. You should only set the milliseconds in your datetime patern if the second fraction is different than milliseconds.

Usage:
`{{ pm_utils.to_timestamp('[expression]') }}`
Expand Down

0 comments on commit 79f9b81

Please sign in to comment.