Not really an issue, but rather another use of the tool that could be advertised in the documentation.

We have slaves that have discrepancies (missing rows, rows with some different values) as highlighted by a very long run of pt-table-checksum. We tried fixing these tables with pt-table-sync with no success.

By running gh-ost on a master using RBR (does not work with statement based replica

sequelize init:models creates a 'models' folder and an index.js file.

What does this do?

How is this intended to be used?

You might consider putting some comments into the file. Would probably save people a lot of hassle trying to figure this out over and over.

Thanks!

Would you be interested in using mypy to validate PEP 484 type annotations as a part of migra's CI? If so, what syntax would you find acceptable? There's:

1. My first choice, python 3.5+ native syntax:

from typing import Union
def foo(a: str, b: int) -> Union[int, str]:
    return b if b else a

2. the other option, python 2.7+ inl

MySQL 8.0 has a lot more reserved words than prior versions (the rationale was to peek ahead at the standard and add them all at once). They are also all accessible via information_schema:

mysql8019> SELECT word FROM information_schema.keywords WHERE reserved=1;
+-------------------------------+
| WORD                          |
+-------------------------------+
| ACCESSIBLE        

@sboosali proposed to port json-schema examples to schematic and document how the json-schema export works, so I'm separating this as an isolated issue.

As you can see, this library is very conservative in regard of json-schema version:
https://github.com/typeable/schematic/blob/master/src/Data/Schematic/JsonSchema.hs#L25

I haven't checked if it's compatible with newer drafts, but it's high

Examples

• get-started (commonjs)
• babel-async-await
• babel-typescript
• typescript
• backup
• docker-backup

I am trying to use yoyo 7.0.0 on Python 3.7 against Postgres 11 on Google Cloud SQL.

I propose there is a significant typo in the yoyo documentation about transactionality.

PostgreSQL
In PostgreSQL it is an error to run certain statements inside a transaction block. These include:

CREATE DATABASE ...
CREATE TABLE