DbUp is a .NET library that helps you to deploy changes to SQL Server databases. It tracks which SQL scripts have been run already, and runs the change scripts that are needed to get your database up to date.
I've pinged Chris to ask if he can officially add that code
That method is included in for Sql Server and one other database that I can't remember offhand, so the documentation is correct but unclear
Running into this weird problem. I want to be able to deploy to multiple databases using a for loop. I am trying to call connection.ChangeDatabase("my_db_name") and then use connection.ConnectionString in the DeployChanges.To.MySqlDatabase(right_here).... but it doesn't specify the DB in that connection string which means it doesn't get used
anyone know a way around that?
@phillijw I suspect the ChangeDatabase command just switches the database for the current connection, the connection string would not be affected as that's only used to establish the connections.
^ thanks. Ended up realizing that before your response
works like a charm
I should probably blog about how I'm setting all this up. I've used other systems before and I'm taking some things I learned from those and applying it with dbup
I can say that I honestly disagree with the sentiment that "ssdt sucks" though. SSDT is actually really really powerful and good and it lets you spit out sql change scripts if you don't trust the automatic deployment features. Modeling the objects in sql is the easiest to work with that I've found so far
i'll share my experience once I have everything set up
Anyone around? I'm having trouble with the mysql beta. I have a DROP/CREATE script which errors out with a dumb message. It works fine in dbForge studio though
Ugh. I wish this had unit tests so I could debug
It seems that it can't handle comments? wut
oh, there has to be a space after the -- in mysql? ugh
perhaps there is or should be a mode I can enable to be verbose in what sql its running because whatever its trying to run is completely broken if I use DELIMITER anywhere
there a target date on the dbup-mysql 4.0 nuget package release? All the other packages were released.
No, sorry. The only thing holding itt up is DbUp/DbUp#169
I currently don't have the time to look into that, but would welcome a PR
Seems easy to fix. Maybe if I knew where to start I could take a look?