Having tried to implement meilisync on a postgres database I encountered some errors

- `meilisync check` did not work because `RealDictCursor` was used as `cursor_factory` and `get_count` used integer indexing, which  `RealDictCursor` does not support

    - I have made my own custom Row and Cursor types that support key indexing and integer indexing

- When deleting something from the database `columntypes` is not included in the payload. `.get` is used to fetch `columntypes` where the length of it is then computed, but `.get` is used without a default, so when it is not included, it would call `len` of `None` which gives an error

    - Added an empty list as default for the various `column` field in the payload

- I am not sure if this is an error, but in the way I want to use meilisync it is. When setting fields for an index in the `config.yml` file, it updates the documents of the index with all the fields for the affected row. This makes search results inconsistent, and could potentially reveal information to the user it should not have.

    - Made it such that when giving fields in the config, it only updates the documents with those given fields. If no fields are given it will include all fields.