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: blog/2023-11-22-why-is-windmill-the-fastest-workflow-engine/index.mdx
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -134,7 +134,7 @@ hand-built workflow engine written on top of the amazing [BEAM](<https://en.wiki
134
134
135
135
There are tons of workflow engines, but not many of them are self-hostable and generic enough to support arbitrary workloads of jobs defined in code,
136
136
and even those have restrictions:
137
-
Some like Airflow and Prefect support only one runtime (Python). Windmill on the other hand supports Typescript/Javascript, Python, Go, Bash and direct SQL queries to BigQuery, Snowflake, Mysql, Postgresql, MSSQL. And its design makes it easy to add more upon request.
137
+
Some like Airflow and Prefect support only one runtime (Python). Windmill on the other hand supports Typescript/Javascript, Python, Go, Bash and direct SQL queries to BigQuery, Snowflake, Mysql, Postgresql, MS SQL. And its design makes it easy to add more upon request.
138
138
Some are notoriously hard to write for (because of complex SDKs, looking at you Airflow's XCOM or Temporal idempotency primitives) and deploy to. Windmill offers an [integrated DX to build and test workflows](/docs/flows/flow_editor) in a few minutes interactively in a mix of raw code for the steps and low-code (or YAML) for the DAG itself. It is also possible to define them wholly with code and full version control using our [VS Code extension](/blog/launch-week-1/vscode-extension).
139
139
140
140
One benefit of being very fast is that it makes running tests very fast too both in terms of latency to start and to run. Wasting time waiting for previews and tests to run is not fun.
In normal mode, workers pull job one at a time, identify the language used by the job (Python, TypeScript, Go, Bash, SnowFlake, PostgreSql, MySql, MSSQL, BigQquery) and then spawn the corresponding runtime then run the job.
306
+
In normal mode, workers pull job one at a time, identify the language used by the job (Python, TypeScript, Go, Bash, SnowFlake, PostgreSql, MySql, MS SQL, BigQquery) and then spawn the corresponding runtime then run the job.
307
307
308
308
Workers run jobs bare, without running containers which gives us a performance boost compared to container based workflow engines. However, for sandboxing purposes, workers themselves can be run inside containers and can run each job in an nsjail sandbox.
Copy file name to clipboardExpand all lines: changelog/2023-12-17-decision-tree/index.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ version: v1.227.0
4
4
title: Decision Tree
5
5
tags: ['App Editor', 'Component']
6
6
image: ./decision-tree.png
7
-
description: This component allows you to create a decision tree. The decision tree is controlled by a flow-like structure. Each node in the tree represents a decision point and can lead to one or more subsequent nodes based on specified conditions.
7
+
description: This app component allows you to create a decision treecontrolled by a flow-like structure. Each node in the tree represents a decision point with a dedicated subgrid and can lead to one or more subsequent nodes based on specified conditions.
Copy file name to clipboardExpand all lines: docs/apps/4_app_configuration_settings/1_app_component_library.mdx
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -127,7 +127,7 @@ The Carousel List component enables duplication of cards or rows with consistent
127
127
128
128
### [Decision Tree](./decision_tree.mdx)
129
129
130
-
This component allows you to create a decision tree. The decision tree is controlled by a flow-like structure. Each node in the tree represents a decision point and can lead to one or more subsequent nodes based on specified conditions.
130
+
This app component allows you to create a decision treecontrolled by a flow-like structure. Each node in the tree represents a decision point with a dedicated subgrid and can lead to one or more subsequent nodes based on specified conditions.
Copy file name to clipboardExpand all lines: docs/apps/4_app_configuration_settings/decision_tree.mdx
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@ import DocCard from '@site/src/components/DocCard';
2
2
3
3
# Decision Tree
4
4
5
-
This component allows you to create a decision tree. The decision tree is controlled by a flow-like structure. Each node in the tree represents a decision point and can lead to one or more subsequent nodes based on specified conditions.
5
+
This app component allows you to create a decision treecontrolled by a flow-like structure. Each node in the tree represents a decision point with a dedicated subgrid and can lead to one or more subsequent nodes based on specified conditions.
Copy file name to clipboardExpand all lines: docs/core_concepts/3_resources_and_types/index.mdx
+32Lines changed: 32 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -180,6 +180,38 @@ _Python_
180
180
/>
181
181
</div>
182
182
183
+
### States Path
184
+
185
+
States are stored in a [path](../16_roles_and_permissions/index.mdx#path) that is unique to the script, script within a flow or schedule. The state path [is defined](https://github.com/windmill-labs/windmill/blob/19547e90c681db1566559c31a508eb093eb05968/backend/windmill-common/src/variables.rs#L150) as:
For example, if a script using states is used within a flow that is scheduled, the state will take a new path as: `folder/flow_path/script_path/schedule_path`, or more concretely: `u/username/u/username/flow_name/u/username/script_name/u/username/schedule_name`.
214
+
183
215
## Using Resources
184
216
185
217
Resources can be used [passed as script parameters](#passing-resources-as-parameters-to-scripts-preferred) or [directly fetched](#fetching-them-from-within-a-script-by-using-the-wmill-client-in-the-respective-language) within code.
title: 'Quickstart PostgreSQL, MySQL, MS SQL, BigQuery, Snowflake'
3
3
slug: '/getting_started/scripts_quickstart/sql'
4
4
---
5
5
6
6
importDocCardfrom'@site/src/components/DocCard';
7
7
8
-
# PostgreSQL, MySQL, MSSQL, BigQuery, Snowflake
8
+
# PostgreSQL, MySQL, MS SQL, BigQuery, Snowflake
9
9
10
10
In this quick start guide, we will write our first script in SQL. We will see how to connect a Windmill instance to an external SQL service and then send queries to the database using Windmill Scripts.
Windmill provides integrations with many different apps and services with the use
28
28
of [Resources](../../../core_concepts/3_resources_and_types/index.mdx). Resources are rich objects in JSON that allow to store configuration and credentials.
29
29
30
-
Each Resource has a _Resource Type_ ([PostgreSQL](https://hub.windmill.dev/resource_types/114/postgresql), [MySQL](https://hub.windmill.dev/resource_types/111/mysql), [MSSQL](https://hub.windmill.dev/resource_types/132/ms_sql_server), [BigQuery](https://hub.windmill.dev/resource_types/108/bigquery), [Snowflake](https://hub.windmill.dev/resource_types/107/snowflake))
30
+
Each Resource has a _Resource Type_ ([PostgreSQL](https://hub.windmill.dev/resource_types/114/postgresql), [MySQL](https://hub.windmill.dev/resource_types/111/mysql), [MS SQL](https://hub.windmill.dev/resource_types/132/ms_sql_server), [BigQuery](https://hub.windmill.dev/resource_types/108/bigquery), [Snowflake](https://hub.windmill.dev/resource_types/107/snowflake))
31
31
that defines the schema that the resource of this type needs to implement. Schemas implement the
@@ -114,7 +114,7 @@ Fill out the form with the information of your MySQL instance and "Test connecti
114
114
| database | string | Database name || true | Created in MySQL (e.g., via phpMyAdmin or MySQL Workbench) or provided by your hosting |
115
115
| password | string | User's password || true | Created in MySQL (e.g., via phpMyAdmin or MySQL Workbench) or provided by your hosting |
116
116
117
-
### MSSQL
117
+
### MS SQL
118
118
119
119
To be able to connect to a [Microsoft SQL Server](https://www.microsoft.com/sql-server) instance, we'll need to define a Resource with the `ms_sql_server` Resource Type first.
120
120
@@ -129,11 +129,11 @@ Fill out the form with the information of your MySQL instance and "Test connecti
129
129
130
130
| Property | Type | Description | Default | Required | Where to Find |
| host | string | Instance host || true | Your hosting provider's control panel or in your server's MSSQL configuration file |
133
-
| port | number | Instance port || false | Your hosting provider's control panel or in your server's MSSQL configuration file |
134
-
| user | string | Username || true | Created in MSSQL (e.g., via SQL Server Management Studio) or provided by your hosting |
135
-
| dbname | string | Database name || true | Created in MSSQL (e.g., via SQL Server Management Studio) or provided by your hosting |
136
-
| password | string | User's password || true | Created in MSSQL (e.g., via SQL Server Management Studio) or provided by your hosting |
132
+
| host | string | Instance host || true | Your hosting provider's control panel or in your server's MS SQL configuration file |
133
+
| port | number | Instance port || false | Your hosting provider's control panel or in your server's MS SQL configuration file |
134
+
| user | string | Username || true | Created in MS SQL (e.g., via SQL Server Management Studio) or provided by your hosting |
135
+
| dbname | string | Database name || true | Created in MS SQL (e.g., via SQL Server Management Studio) or provided by your hosting |
136
+
| password | string | User's password || true | Created in MS SQL (e.g., via SQL Server Management Studio) or provided by your hosting |
137
137
138
138
### BigQuery
139
139
@@ -262,7 +262,7 @@ You can directly "Test connection" if needed.
262
262
## Create Script
263
263
264
264
Next, let's create a script that will use the newly created Resource. From the <ahref="https://app.windmill.dev/"rel="nofollow">Home</a> page,
265
-
click on the "+Script" button. Name the Script, give it a summary, and select your preferred language, [PostgreSQL](#postgresql-1), [MySQL](#mysql-1), [MSSQL](#mssql-1), [BigQuery](#bigquery-1), [Snowflake](#snowflake-1).
265
+
click on the "+Script" button. Name the Script, give it a summary, and select your preferred language, [PostgreSQL](#postgresql-1), [MySQL](#mysql-1), [MS SQL](#ms-sql-1), [BigQuery](#bigquery-1), [Snowflake](#snowflake-1).
266
266
267
267

0 commit comments