Gyula Bibernáth
Gyula Bibernáth
It seems to work for _ONLY ONE computed value for ALL ROWS_ in the given column, not for different values in different rows like: id comp 1 id+1 2 id-1
It still exists in version 2.9.0. It is really annoying, since it is a runtime error + there is absolutely no sign where the problem is or what type is...
Actually the same error happens already with gradle version 6.x Until it's fixed as a workaround to make it run with at least **gradle version 6.x** the underlying solidity and...
The solution I'm using is a new concept: in the current official implementation only `properties` are available: their values are set when the script is written like `constant` in programming...
Do you create a branch for it in this repo or I should publish it with a different org id?
Simply restructuring the XSD can prevent this cases. I have a working solution, just need some more time to fully test it.
I believe fixing the XSD is way more helpful for the users, because the XSD aware IDEs/editors can help avoiding such errors. Plus the Xerces parser use the same XSD,...
For `include` it does not make sense. `preConditions` is available of the `databaseChangeLog` in the included file...
> Hi @b-gyula, > > As mentioned above, I think it would be good to split up this PR into smaller pieces. We are thinking of taking part of the...
You can have multiple `preConditions` on the `databaseChangeLog` level in ALL formats except XML