Carsten Brandt

Migration for new fields: Use AFTER to keep order as in schema

1

Migrations for adding new columns should use "AFTER" keyword to make sure order of columns is the same as in schema.

timestamp migrations do not work in MariaDB

4

```yaml Customer: description: customer is the one that orders a campaign type: object required: - id - name - created_at properties: id: type: integer name: type: string maxLength: 100 created_at:...

As of the [release of OpenAPI 3.1](https://github.com/OAI/OpenAPI-Specification/releases/tag/3.1.0-rc0) and OpenAPI Schema is now fully compatible with JSON Schema: > The Schema Object is now fully compliant with JSON Schema draft 2019-09...

API: Batch queries with transactions support and error handling.

21

follow up on #303

- adjusted code style for all chapters - improved readablility and changed files to use consistent code style - also fixed some very minor issues

it should include the process of adding parenthesis to allow simpler override in sqlite\QueryBuilder. Currently the complete build() method is overridden just to add two parenthesis.

as a followup to #8644 / #11775: getting all tables and views should be consistent across schema implementations.