Ondřej Švanda

Hi, thank you for the repository, I was able to reproduce it locally, and find the issue. ### Investigation Initially, I thought the issue was caused by the 3rd party...

Running all migrations in a single transaction is IMO the better option _if the database engine supports it_. The reason is that if we update an application running in production,...

@igalklebanov > How come? It's the entire reason for the original post - apparently, in Postgres, you can't add a new enum value _and then use it_ within the same...

I looked at MikroORM, but couldn't figure out how to make it work together with their notion of entity managers. All other adapters work by having access to a single...

Is this adapter still needed? MikroORM now comes with their own [`@Transactional` decorator](https://mikro-orm.io/docs/transactions#approach-2-explicitly).

I'll go ahead and close this as not planned, as per my previous comment, I don't see a reason to re-implement a sub-par version of the same feature that MikroORM...

I would also be interested in this feature. The current detection of breaking/non-breaking changes is insufficient for most common scenarios - e.g. changing the payload of messages in terms of...

Sadly, I have not. It turned out that manual classification of breaking changes was enough for the project at that time, give the size of the team. I've since moved...

@in-live-md Have you ever found a solution? I'm facing exactly the same issue when migrating a Vue 2 project to Vite.

Hi, the goal of this library is to abstract away transactions, so that the code executing the query doesn't have to care whether it's run within a transaction or not,...