Alexey Palazhchenko

> Conditions that I'm not sure In that case, we use integration tests to do the same thing as MongoDB. Please add a test [there](https://github.com/FerretDB/FerretDB/blob/ba09c95bce842570ecb39ea854d07d5b51fe450e/integration/query_evaluation_test.go#L412). See [there](https://github.com/FerretDB/FerretDB/blob/main/CONTRIBUTING.md#code-overview) for an overview...

See: * https://github.com/FerretDB/FerretDB/blob/8d3027ebd80a3a7400b4d996fe5d05290f91ba15/Taskfile.yml#L240-L244 * https://github.com/FerretDB/FerretDB/blob/main/integration/Taskfile.yml `task`'s `-d` flag does the trick

> Also, do you want to get rid of .golangci-new.yml? and write exclude rules in .golangci.yml? `.golangci-new.yml` contains new linters that check only new code: https://github.com/FerretDB/FerretDB/blob/2786a4d33e98be0bae6bcdb1810083704ee1f07b/.golangci-new.yml#L128 For example, we decided...

> Do you expect in this PR to skip all these failing linters for integration? I think yes, as a temporary measure

Done in #1200

v0.8.2 was released, but this issue (and milestone) is still open.

How about https://github.com/gofrs/uuid?

:+1:

> There is not really a "nil date" since time.Time is a number. `*time.Time` can be `nil`. Right now there is no way to store it in database.

Nor `*string`, `*bool`, etc., but they work across most drivers. Probably due to different interpretations of > It is either nil or an instance of one of these types Specifically,...