Rodel E. Dagumampan

Hi @kirill-gerasimenko , thanks again for reaching out. The tool can only get better with valuable feedback like this. I was able to reproduce your case. I found that this...

@kirill-gerasimenko, yes unfortunately you would have to call yuniql run twice to split the transaction. Each migration is one atomic transaction so far. I think I will create a new...

Yes. This is not pretty and we'll prioritize this per version transaction support. I think its more pressing to implement this feature now after your feedback. In the sample above...

> > Each migration is one atomic transaction so far. > > What you are saying is that for example if I have to update the database which for example...

Yes, I forsee different transaction modes `full (default)`,`per-version`,`none`. The `full` is the default for all platforms supporting transactional DDL, the `per-version` best fit in your scenario where some scripts really...

> Did you think about having some compensation scripts, when you kind of `undo` the version? With this per-version transaction this might help to clean up the version that has...

I think the choice of transaction mode largely depends of the nature of pending versions to be applied. This also is limited to cases where you have mixed .sql and...

Everything are based on CLI parameters so its always customizable. The azure pipelines tasks of yuniql also uses CLI to run the tasks and we can make a variable the...

Hi @avengerovsky , thanks for reaching out and you're probably right about this. I will add some test to cover this and fix will possibly be in the next release....

@avengerovsky , I tried to reproduce this and I think that while it prints incorrectly on console, it reads the content of the script files correctly. Here I have an...