User profile for Peter_Laws

Hello, After a thorough investigation we've been unable to replicate the reported issue. Would you be willing to supply a project that demonstrate the problem so we can find the root cause? / comments

Hello,After a thorough investigation we've been unable to replicate the reported issue.Would you be willing to supply a project that demonstrate the problem so we can find the root cause?

0 votes

Hello Titanic, Thank you for raising this. Are you using error reporting via the SDK or the Smart Assembly application please? Additionally, are you using a custom web server of your own for the reporting or are the reports coming in via our service? / comments

Hello Titanic,Thank you for raising this. Are you using error reporting via the SDK or the Smart Assembly application please?Additionally, are you using a custom web server of your own for the repo...

0 votes

Hello Fredrik_S, Thank you for the excellent question! Firstly, an implicit behavioural element that may not be immediately obvious, if you have multiple baselines, flyway will only use the newest, this is the preferred way to handle changing requirements. By extension, but arguably optionally, is the idea of 'rebaselining' which is to consolidate all your existing changes into a new baseline. This can be useful when as time progresses, the sum of all your migrations accumulates technical debt over time and due to ever-changing business requirements have become bloated with changes back and forth. As a result, drawing a proverbial line in the sand and reconstituting all those changes into a single baseline which becomes your new source of truth that you operate from can be very useful. In practical terms that means you either package up your existing migrations and remove them from Flyway Desktop, your you start a new project for the purpose of generating this baseline. The exact choice of adding this to the existing scripts, or replacing them wholesale is best done on a case by case basis, how many environments it will affect is commonly the most impactful consideration. Lastly, a couple of clarifications on some of your points. validateOnMigrate doesn't validate your sql code. What it does is prepend your Migrate verb with a validate verb, the purposes of which is to verify that the scripts available match the scripts that are known. I.E A safety net to highlight if anyone snuck an alteration into a script between when it was last run and now. The exception you're seeing is direct from the db, not flyway and as such can't really be ignored. You could potentially suppress the error if you intend to deal with it through some other means. But I would use that approach sparingly as you could easily make a rod for your own back by continuing instead of addressing the issues. See flyway error overrides / comments

Hello Fredrik_S,Thank you for the excellent question!Firstly, an implicit behavioural element that may not be immediately obvious, if you have multiple baselines, flyway will only use the newest, t...

0 votes

This can sometimes occur if there isn't complete parity between the available .Net versions on the machine that that authored the code and the build machine. I'd recommend comparing them via a dotnet --info command. / comments

This can sometimes occur if there isn't complete parity between the available .Net versions on the machine that that authored the code and the build machine.I'd recommend comparing them via a dotne...

0 votes

Hello mohammad.hafizullah, There's presently no SSH integration in Flyway Desktop, to achieve this you'd need to initiate something like a PuTTY session first, and then connect with Flyway Desktop. / comments

Hello mohammad.hafizullah,There's presently no SSH integration in Flyway Desktop, to achieve this you'd need to initiate something like a PuTTY session first, and then connect with Flyway Desktop.

0 votes

Hi Stevie1, Almost nothing, it was a minor bump to publish the nuget packages with 8.3.0 unintentionally missed. I think there was also a very minor bug fix for a rare edge case of config mishandling. / comments

Hi Stevie1,Almost nothing, it was a minor bump to publish the nuget packages with 8.3.0 unintentionally missed.I think there was also a very minor bug fix for a rare edge case of config mishandling.

0 votes

Hello, I'm afraid we got a little excited and updates our release notes a little early. This version of Smart Assembly which supports .Net 8 is in closed beta, this is also why the nuget package has not been updated. To avoid further confusion the release notes have been reverted until the version is release to general availability. Please accept our apologies for the confusion, we hope to go GA with this version in the very near future. / comments

Hello, I'm afraid we got a little excited and updates our release notes a little early. This version of Smart Assembly which supports .Net 8 is in closed beta, this is also why the nuget package ha...

0 votes

I've just noticed your post was marked as a discussion rather than a question, I've just altered it. Do you now have the option to mark it as answered? You may need to refresh. / comments

I've just noticed your post was marked as a discussion rather than a question, I've just altered it.Do you now have the option to mark it as answered? You may need to refresh.

0 votes

My pleasure virajb, if our answers are helpful please consider marking them as an accepted answer, to help others members of the community find useful information. Have a good week. / comments

My pleasure virajb, if our answers are helpful please consider marking them as an accepted answer, to help others members of the community find useful information.Have a good week.

0 votes

Hello virajb, Thank you for the question. Your understanding is indeed correct, it should be invoked as needed, not as a matter of course. There are multiple reasons for this. As you highlighted, the safety net of checksum changes, in the current configuration, someone could essentially make silent modifications and were this then later run against a new environment, you would have disparate results. Showing failed migrations is particularly desirable if you have multiple people contributing as it will highlight existing issues, making it easier to avoid compounding them. Lastly, something often missed is that repair is a targetted command just like migrate. So if the locations were to change in your pipeline for migrate alone, the unmodified repair command would then most likely not do what you were intending and on the next run, remove all the applied migration that it couldn't resolve. (source) The intention of repair should effectively be 'maintenance mode' in the event manual intervention is required. / comments

Hello virajb,Thank you for the question. Your understanding is indeed correct, it should be invoked as needed, not as a matter of course. There are multiple reasons for this.As you highlighted, the...

0 votes

How can we help you today?

Peter_Laws

Comments