Tags: alchemy-swift/alchemy
Tags
Adds support for TLS & HTTP/2 (#69) By default, the server runs over HTTP/1.1. To enable running HTTP/1.1 over TLS, use useHTTPS. To enable HTTP/2 upgrades (will prefer HTTP/2 but still accept HTTP/1.1 over TLS), use useHTTP2. Note that the HTTP/2 protocol is only supported over TLS, so implies using it. Thus, there's no need to call both useHTTPS and useHTTP2; useHTTP2 sets up both TLS and HTTP/2 support.
Lots of fixes around MySQL (#53) Big thing is that insert behavior is deferred to the Grammar so that MySQL can do it custom. By default, MySQL now runs two queries, one to insert and one to pull the recent item. `insertAll()` also is now separate, consecutive queries in MySQL. The user can opt out of this (single query for insert and insertAll) by passing `returnItems: false` to `QueryBuilder.insert`. This also... Adds - `ON DELETE` and `ON UPDATE` to migration builders - bigInt type and `UNSIGNED` modifier to migration builders - Revamped column constraint building to add most constraints separately, at the end of a `CREATE TABLE` statement since the shortcuts I was using weren't all compatible across Postgres and MySQL Fixes - Issue with SQL columns not being populated if `.select` wasn't called in query builder (Postgres accepted it with no *, MySQL did not. That's why it didn't get caught) - Adds some missing date time types for parsing from MySQL - Fix constraint issues that were borked on MySQL. Tested all the Quickstart endpoints on Postgres/MySQL to confirm nothing else is missing. Also updated the quickstart migrations to use `.unsigned` and `.bigInt` for some columns by default, since even tho it works fine with Postgres without, MySQL requires them. Co-authored-by: Chris Anderson <hi@chrisanderson.io>
PreviousNext