You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/development.md
+16Lines changed: 16 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,22 @@ Before you begin, ensure you have the following installed on your machine. Exact
11
11
* OpenJDK >= 11
12
12
* Python >= 3.9 < 3.13
13
13
14
+
### Windows Prerequisites
15
+
16
+
The development environment of SQLMesh depends both on:
17
+
18
+
* Symbolic links in the repository which, whilst available on Windows, typically require additional permissions for the process running git, and;
19
+
* Some Python functionality (e.g. `SIGUSR1`) that is only available on UNIX systems. Whilst this functionality is gated so shouldn't error on Windows, the development container enables its use.
20
+
21
+
For the Python functionality, a development container is provided to develop against Ubuntu 24 with Python 3.12.
22
+
23
+
For symbolic links, you must ensure that when checking out the repository:
24
+
25
+
* The git configuration `core.symlinks` is set to `true` (this also needs to be done before bind mount, i.e. when the development container is started)
26
+
* The process that git runs as is permitted to create symbolic links. This can typically be done by running git as an administrator, or enabling [developer mode on Windows](https://learn.microsoft.com/en-us/windows/advanced-settings/developer-mode).
27
+
28
+
Development containers are supported by [a number of IDEs](https://containers.dev/supporting.html). For developers using VSCode, [Microsoft has a tutorial on how to use development containers](https://code.visualstudio.com/docs/devcontainers/tutorial).
29
+
14
30
## Virtual environment setup
15
31
16
32
We do recommend using a virtual environment to develop SQLMesh.
Copy file name to clipboardExpand all lines: docs/guides/multi_engine.md
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,9 +11,13 @@ SQLMesh enables this decoupling by supporting multiple engine adapters within a
11
11
Configuring your project to use multiple engines follows a simple process:
12
12
13
13
- Include all required [gateway connections](../reference/configuration.md#connection) in your configuration.
14
-
- Specify the `gateway` to be used for execution in the `MODEL` DDL.
14
+
- Set `model_defaults.gateway` to the gateway most models should use, and override individual models
15
+
with `gateway` in the `MODEL` DDL when needed.
15
16
16
-
If no gateway is explicitly defined for a model, the [default_gateway](../reference/configuration.md#default-gateway) of the project is used.
17
+
If no gateway is explicitly defined for a model, SQLMesh uses the project's
18
+
[`model_defaults.gateway`](../reference/model_configuration.md#model-defaults), when configured,
19
+
and otherwise uses its [default_gateway](../reference/configuration.md#default-gateway). This lets
20
+
all managed models in a project use a gateway without repeating it in every model definition.
17
21
18
22
By default, virtual layer views are created in the `default_gateway`. This approach requires that all engines can read from and write to the same shared catalog, so a view in the `default_gateway` can access a table in another gateway.
0 commit comments