@@ -80,10 +80,7 @@ dbt_sqlite:
80
80
# files in schemas_and_paths as long as there's no conflicts.
81
81
schema_directory : ' /my_project/data'
82
82
83
- # optional: list of file paths of SQLite extensions to load. see README.
84
- # crypto.so is needed for snapshots to work
85
- # math.so is needed for ceil function
86
- # text.so is needed for split_part macro to work
83
+ # optional: list of file paths of SQLite extensions to load. see README for more details.
87
84
extensions :
88
85
- " /path/to/sqlean/crypto.so"
89
86
- " /path/to/sqlean/math.so"
@@ -107,8 +104,8 @@ and schemas.)
107
104
get attached when database connection is created.
108
105
109
106
- If dbt needs to create a new schema, it will be created in ` schema_directory `
110
- as ` schema_name.db ` . Dropping a schema results in dropping all its relations
111
- and detaching the database file from the session.
107
+ as ` schema_name.db ` . Dropping a schema results in dropping all its relations,
108
+ detaching the database file from the session, and deleting the file .
112
109
113
110
- Schema names are stored in view definitions, so when you access a non-'main'
114
111
database file outside dbt, you'll need to attach it using the same name, or
@@ -131,7 +128,7 @@ not worth the effort.
131
128
## SQLite Extensions
132
129
133
130
These modules from SQLean are needed for certain functionality to work:
134
- - ` crypto ` : provides ` md5() ` function needed for snapshots
131
+ - ` crypto ` : provides ` md5 ` function needed for snapshots
135
132
- ` math ` : provides ` ceil ` and ` floor ` needed for the datediff macro to work
136
133
- ` text ` : provides ` split_part ` function
137
134
0 commit comments