Support for Beta and Live database

Hello,

I have a feature request. Can you save all major querys to a separate file and give the option to execute them on another database? It would be nice if I could just set a database as Beta and another database as Live. All CREATE, ALTER and DROP querys I executed on Beta, can be executed on the Live server very easy. I think this is a great feature and not that much work to implement. What are your thoughts?

Mart-Jan

That's a weird workflow, isn't it? You don't normally deploy to Production something that haven't been tested and that scenario assumes you already wrote the migration scripts. You aren't going to compose the scripts on-the-fly, without any error or correction. Unless when you say major queries you actually expect some kind of intelligence, like, "this INSERT query took three attempts to get right, just run the third one when in Production mode".

Sorry but I don't get it. Of course, HeidiSQL developer will have the last word but...

I'm thinking the same as kalvaro. Quite a weird idea to do that in the direction beta => production. And even more weird to have such a feature in some specific client application, which does not need to be the same for all users.

Apart from that, there is already master/slave replication mechanism in MySQL itself. This even works regardlessly of the client application.

Most of the time, I forget the ALTER querys I runned on beta environment. And it would be awesome to have a list of only the ALTER querys so that I can see what the changes are for the latest release. The CREATE querys should only be added when executed successfully. If the tables are Altered after the CREATE, that would be less efficient, but you are sure the tables on Production will be exactly the same as on Beta.

Apart from a master/slave configuration you can use HeidiSQL's SQL export from your beta to production server from time to time. Check the "Drop tables" and "Create tables", and click "Export".

But I do not want to drop tables since there is Live data in it...

Well, then use a master/slave configuration.