Comments
Sort by recent activity
Excellent news! I hope your project goes well, should you have any questions or issues, please don't hesitate to raise it with support. / comments
Excellent news! I hope your project goes well, should you have any questions or issues, please don't hesitate to raise it with support.
Hi Lauther, Thanks for the question. Yes as you've observed, the default implementation contains a timestamp to maximise the probability that no duplicate migration file names may be created. However this may be more caution that your use case merits, especially if you only have a few people generating migrations. Happily Flyway Desktop will seeks to match the format of the preceding migration, as shown here. I've removed the timestamp on my most recent migration (003), and the subsequent file name offered by Flyway Desktop when I generate my next migration is 004. [image] [image] Hope this helps! / comments
Hi Lauther, Thanks for the question. Yes as you've observed, the default implementation contains a timestamp to maximise the probability that no duplicate migration file names may be created. Howev...
Hello kcm, When you say config, do you mean configuration like filters, comparison options etc or the actual source control definition itself, such as targeted db, repository location and the like for distribution? / comments
Hello kcm, When you say config, do you mean configuration like filters, comparison options etc or the actual source control definition itself, such as targeted db, repository location and the like ...
Hello Arcadia, Please see see the following documentation of the 'yours' vs 'theirs' behaviour. https://documentation.red-gate.com/soc/common-tasks/resolve-and-merge-conflicts There is a seperate section for static data further down that should also be applicable. It's detailed in the above link, but essentially for practical purposes, the 'take theirs' option is just discarding your changes so that you're free to pull down the latest version. Naturally if you're using any of the mentioned 3rd party tool to get a row by row merge, the outcome will be different. / comments
Hello Arcadia, Please see see the following documentation of the 'yours' vs 'theirs' behaviour.https://documentation.red-gate.com/soc/common-tasks/resolve-and-merge-conflictsThere is a seperate sec...
Hello, Yes the baseline functionality is for exactly this scenario, please see the following resources. Command: https://flywaydb.org/documentation/command/baseline Example: https://flywaydb.org/documentation/usage/commandline/baseline Config parameter: https://flywaydb.org/documentation/configuration/parameters/baselineVersion / comments
Hello,Yes the baseline functionality is for exactly this scenario, please see the following resources. Command: https://flywaydb.org/documentation/command/baselineExample: https://flywaydb.org/docu...
Hello Sol, Thank you for highlighting this issue, it's being tracked on our ref SA-2476, once addressed you'll be able to see that reference in the release notes. I should warn you that we're presently focusing on adding .Net 6 support to the .Net tools and that presently has priority. / comments
Hello Sol,Thank you for highlighting this issue, it's being tracked on our ref SA-2476, once addressed you'll be able to see that reference in the release notes. I should warn you that we're presen...
Hello Sol, Thank you for your patience with us regarding issue SA-2476. Our development team have now reviewed the bug you have identified and highlighted to us alongside our current workload and available resources. Unfortunately, on this occasion this is not something they are able to provide a fix for. We do appreciate the effort our customers go to working with us to better our products, and so please do continue to highlight anything you find that needs our attention. We know this isn't the answer you were hoping for, thank you for trying to help us to improve our product. / comments
Hello Sol,Thank you for your patience with us regarding issue SA-2476.Our development team have now reviewed the bug you have identified and highlighted to us alongside our current workload and ava...
Yes agreed, @PSnape, a separate issue for the invalid memory would be appropriate please. / comments
Yes agreed, @PSnape, a separate issue for the invalid memory would be appropriate please.
Good morning, We've just released Smart Assembly v8.2.0 which substantively overhauls the dependency resolver, please could you update and let us know your findings? / comments
Good morning,We've just released Smart Assembly v8.2.0 which substantively overhauls the dependency resolver, please could you update and let us know your findings?
Hello JeffElliott, Thank you for sharing your findings, Smart Assembly should automatically detect the bitness but given the nature of this dependency resolution issue, that could too be compromised. The issue you'd described (ref SA-2490) is our current focus concurrently with .Net 7 support, we hope to have a release addressing this in the near future. If you don't need .Net 6 support for your application, you could work around the issue by dropping to a version preceding v8.1.1 where the issue was introduced, while we work on a solution. Please accept our apologies for the inconvenience this issue has caused. / comments
Hello JeffElliott,Thank you for sharing your findings, Smart Assembly should automatically detect the bitness but given the nature of this dependency resolution issue, that could too be compromised...