Breaking changes should be published with major releases

Problem

The recent 2.9.0 library update has created quite a few issues since apparently the findOne function can’t be called on non-unique columns anymore. This breaking change (at least for TypeScript) was quite unexpected.

Suggested solution

Please release breaking changes like those with major version releases, e.g.: 3.x

Alternatives

Show a disclaimer in the CLI or on the website or implement feature flags that default to the old behaviour until a next major version release.

Additional context

While always dragging features like this out to the next major version may hinder innovation inertia, I think this should be taken into consideration for a ORM which is a major building block for applications and should thus be relatively stable in its API.

[dnlsndr]

Great! Yeah seems like we didn’t use the right function, it was simple to change anyways. I’ll close this issue since there seems to be no real problem.

[thebiglabasky]

Thanks for these details!

It looks like the previous behaviour wasn’t what we expected, so this may have been an unknown “bug” that got fixed with 2.9.0 as a side effect.

For your use case, you can now use findFirst which allows doing basically what your findOne was doing so that findOne is indeed giving the strictness guarantee. It hopefully comes down to a search and replace.

I acknowledge the mishap and will check with the team if something changed.