add experimental support for Microsoft SQL Server

Author: lovasoa

CHANGELOG.md

@@ -1,6 +1,6 @@
 # CHANGELOG.md
 
-## unreleased
+## 0.9.0 (2023-07-30)
 
  - Added a new `json` component, which allows building a JSON API entirely in SQL with SQLPage !
    Now creating an api over your database is as simple as `SELECT 'json' AS component, JSON_OBJECT('hello', 'world') AS contents`.
@@ -9,6 +9,7 @@
  - Update the database drivers to the latest version, and switch to a fork of `sqlx` that opens the door to supporting Microsoft SQL Server in the future. This also updates the embedded version of SQLite to 3.41.2, with [many cool new features](https://www.sqlite.org/changes.html) such as:
    - better json support
    - better performance
+ - Add experimental support for *Microsoft SQL Server*. If you have a SQL Server database lying around, please test it and report any issue you might encounter !
 
 ## 0.8.0 (2023-07-17)
 

Cargo.lock

@@ -17,7 +17,7 @@ panic = "abort"
 codegen-units = 2
 
 [dependencies]
-sqlx = { package = "sqlx-oldapi", version = "0.6.5", features = ["any", "runtime-actix-rustls", "sqlite", "postgres", "mysql", "chrono"] }
+sqlx = { package = "sqlx-oldapi", version = "0.6.7", features = ["any", "runtime-actix-rustls", "sqlite", "postgres", "mysql", "mssql", "chrono"] }
 chrono = "0.4.23"
 actix-web = { version = "4", features = ["rustls", "cookies"] }
 percent-encoding = "2.2.0"

Cargo.toml

@@ -85,6 +85,7 @@ WHERE $first_name IS NOT NULL;
 - [sqlite](https://www.sqlite.org/index.html)
 - [PostgreSQL](https://www.postgresql.org/), and other compatible databases such as *YugabyteDB*, *CockroachDB* and *Aurora*.
 - [MySQL](https://www.mysql.com/), and other compatible databases such as *MariaDB* and *TiDB*.
+- [Microsoft SQL Server](https://www.microsoft.com/en-us/sql-server), and all compatible databases and providers such as *Azure SQL* and *Amazon RDS*.
 
 ## How it works
 

README.md

@@ -275,6 +275,7 @@ using a function to convert the rows into a json array like
  - `json_group_array()` in SQLite,
  - `json_agg()` in Postgres, or
  - `JSON_ARRAYAGG()` in MySQL.
+ - `FOR JSON PATH` in Microsoft SQL Server.
 
 
 In SQLite, the query would look like

examples/official-site/sqlpage/migrations/01_documentation.sql

@@ -36,6 +36,7 @@ To build a json array out of rows from the database, you can use:
  - `json_group_array()` in SQLite,
  - `json_agg()` in Postgres, or
  - `JSON_ARRAYAGG()` in MySQL.
+ - `FOR JSON PATH` in SQL Server.
 
 
 ```sql

examples/official-site/sqlpage/migrations/11_json.sql

@@ -98,6 +98,7 @@ Later, when you want to deploy your website online, you can switch back to a per
  - a SQLite file with `sqlite://your-database-file.db` ([see options](https://docs.rs/sqlx/0.6.3/sqlx/sqlite/struct.SqliteConnectOptions.html#main-content)),
  - a PostgreSQL-compatible server with `postgres://user:password@host/database` ([see options](https://www.postgresql.org/docs/15/libpq-connect.html#id-1.7.3.8.3.6)),
  - a MySQL-compatible server with `mysql://user:password@host/database` ([see options](https://dev.mysql.com/doc/refman/8.0/en/connecting-using-uri-or-key-value-pairs.html)),
+ - a Microsoft SQL Server with `mssql://user:password@host/database`,
  
 For more information about the properties that can be set in sqlpage.json, see [SQLPage''s configuration documentation](https://github.com/lovasoa/SQLpage/blob/main/configuration.md#configuring-sqlpage)
 

examples/official-site/your-first-sql-website/index.sql

@@ -289,6 +289,7 @@ impl Database {
                     AnyKind::Postgres => 50,
                     AnyKind::MySql => 75,
                     AnyKind::Sqlite => 16,
+                    AnyKind::Mssql => 100,
                     #[allow(unreachable_patterns)]
                     _ => unreachable!("unsupported database"),
                 }