Sculas

@oSumAtrIX I think it's better to leave the PR as-is right now. It's better to just have it be "wrong" and then fix it later than doing a half-assed implementation...

That'd require a whole new repository and new IntegrationsPatch dependency for.. just this? And for it then all be removed when everything is refactored into how you said it would...

It seems that you're using an incompatible version of patches and cli. Please update both to the latest version.

Of course, but it doesn't exist yet.

You don't need to add both, adding `#[serde(skip)]` does the same.

Does this also account for mock databases?

@tyt2y3 looks like you deleting the branch closed the PR. Maybe target the PR to master and reopen?

Any updates on this?

Would an error like `UniqueConstraintError` be out of scope for SeaORM? If not, maybe some other uncommon errors too? Just to make it easier for the user. If it's not...

> This is needed very often when writing applications. Yeah. I currently have some function that matches the error and checks if it's a unique constraint violation. It would be...