Comments
Sort by recent activity
Hello Jaya, I'm sorry to say at present, .Net 7 isn't yet supported by Smart Assembly. https://documentation.red-gate.com/sa/getting-started/requirements We will update the forum and release notes when that changes. / comments
Hello Jaya,I'm sorry to say at present, .Net 7 isn't yet supported by Smart Assembly.https://documentation.red-gate.com/sa/getting-started/requirementsWe will update the forum and release notes whe...
Hello fvargas, The banner below the locked fields implies you have the standard edition rather than the pro edition, please could you confirm if that's so? The trial you were using is the full Professional edition. The different functionality is detailed at the bottom of this page https://www.red-gate.com/products/sql-compare/ and in more detail on this page, https://documentation.red-gate.com/sc/setting-up-the-comparison/setting-data-sources, under 'Selecting data sources'. / comments
Hello fvargas,The banner below the locked fields implies you have the standard edition rather than the pro edition, please could you confirm if that's so?The trial you were using is the full Profes...
Hi yohei, Thanks for the question! Flyway supports both Script migrations and SQL Migrations and from your phrasing it sounds like you're trying to blend those together into a single file. Please see https://documentation.red-gate.com/fd/migrations-184127470.html under for mroe detail on Script migrations. You said Jinja is python based and flyway does support .py file, so there may be a happy medium for what you need. I'd expect that you could have branching logic in your script that then invoked the desired behaviour using this format. / comments
Hi yohei,Thanks for the question!Flyway supports both Script migrations and SQL Migrations and from your phrasing it sounds like you're trying to blend those together into a single file.Please see ...
Hi vinceggwp, I suspect what you're thinking of is actually an automatic transaction rollback, but it will look a lot like an undo. This behaviour is db specific, SQL Server supports it automatically, assuming you're performing a migration on code that can be encapsulated in a transaction. Whereas Oracle can't rollback due to implicit commits. You said you're using PG, it won't do it automatically, reading https://www.postgresql.org/docs/current/tutorial-transactions.html I'm not sure it's possible to do it automatically regardless of flyway. As such, if you flyway migration fails, it will display as failed in the schema history and will require you to run the repair command. / comments
Hi vinceggwp,I suspect what you're thinking of is actually an automatic transaction rollback, but it will look a lot like an undo. This behaviour is db specific, SQL Server supports it automaticall...
We don't have much documentation regarding a DinD scenario, the following is the closest I know of, it might provide some useful points if you're not very familiar with DinD, Dockerized flyway. There isn't a dedicated 'don't run repeatable migrations' option as that's diametrically opposed to their intention. I think the path of least resistance of what you'd described would be to put all the repeatable migrations in a separate directory (please remember to link it via flyway locations) so they can be more easily programmatically addressed, then not include them and use the ignoreMigrationPatterns switch to get the behaviour you want. In this instance -ignoreMigrationPatterns="repeatable:missing". I'm afraid I've had very little exposure to the documentation side, so I'll leave that for the community to comment if there are any 3rd parties they'd recommend. / comments
We don't have much documentation regarding a DinD scenario, the following is the closest I know of, it might provide some useful points if you're not very familiar with DinD, Dockerized flyway.Ther...
Thank you for the question seppe! That is indeed fairly niche, I have a few thoughts, though given your description I'm not certain how impactful they may be. You could potentially reduce the load by reducing the number of transactions. That would commit you to more 'all or nothing' migrations, but given this testing scenario I think that may be serviceable? flyway migration transaction grouping You may find some saving with containerisation as you could then generate your environment on demand with a small round trip time? Again, contingent upon this being more advantageous than your existing configuration. The last point is the most ambitious, I don't know if you're using our comparison technology. This advice is a viable optimisation strategy regardless, but I feel more comfortable recommending it for our users because it's a lot less effort and that's what we term 'rebaselineing', wherein you consolidate all migrations into a single script (baseline) and in the process de-duplicate changes. Naturally the benefits here are variable depending on your development practices and diversity of business needs influencing change. / comments
Thank you for the question seppe!That is indeed fairly niche, I have a few thoughts, though given your description I'm not certain how impactful they may be.You could potentially reduce the load by...
Hi beerbox (excellent name!) This is possible, there are two possible ways to achieve this. 1. Callbacks are the preferred mechanism as it gives you timing granularity. As you can see from the linked list, you can trigger arbitrary code exactly when you want it. 2. You can overcome the repeatable migration safety feature by adding a variable to it that ensures the script checksum will always be different. An example of this is detailed here. https://flywaydb.org/blog/flyway-timestampsandrepeatables / comments
Hi beerbox (excellent name!)This is possible, there are two possible ways to achieve this.1. Callbacks are the preferred mechanism as it gives you timing granularity. As you can see from the linked...
It could be related to the version, we've certainly released many fixes between then and now. Are you supplying any other versions parameters beyond what you listed earlier please? The are multiple factors it could be, Target for instance. To be certain, the full console input would be useful, with debug output. Since that could contain sensitive information, I can raise a support ticket for you and contact you directly to give you a secure means to provide the information, if you like? / comments
It could be related to the version, we've certainly released many fixes between then and now.Are you supplying any other versions parameters beyond what you listed earlier please? The are multiple ...
Hello chinmoy87, I anticipate your issue is that you're attempting to redefine a baseline migration as a version migration which is liable to cause some confusion. Additionally what flyway version are you using please? I've only ever seen that command as 'baselineMigrationPrefix'. As shown, that baseline approach you've taken is perfectly valid by itself.[image] [image] / comments
Hello chinmoy87,I anticipate your issue is that you're attempting to redefine a baseline migration as a version migration which is liable to cause some confusion. Additionally what flyway version a...
Thank you for your question CLVogel, I'm afraid there's no automatic scanning for such, but yes, you can provide the tooling pointers to follow to guard elements you recognise should be obfuscated. Please see https://documentation.red-gate.com/sa/using-custom-attributes / comments
Thank you for your question CLVogel,I'm afraid there's no automatic scanning for such, but yes, you can provide the tooling pointers to follow to guard elements you recognise should be obfuscated.P...