How to skip USE DatabaseName from Schema/Data Sync Scripts

Discussion of open issues, suggestions and bugs regarding database management and administration tools for MySQL
Post Reply
Justmade
Posts: 108
Joined: Sat 16 Aug 2008 03:51

How to skip USE DatabaseName from Schema/Data Sync Scripts

Post by Justmade » Tue 01 Feb 2011 04:39

I have to generate Sync Script that might have to be run in many different computer with different database name by my own program, which will select the target database before running the script.

However, I can see no place to skip that Use statement.

As I need to automate the script generating process (I plan to use your command line operation), it would be very usefully to have an an options to skip that.

Thanks you very much.

.jp
Devart Team
Posts: 345
Joined: Wed 09 Sep 2009 06:55
Location: devart

Post by .jp » Tue 01 Feb 2011 08:52

Alas, there is no option to exclude USE clause in the update script.
But, we have definite plan to add this option in the next version of the products.

Justmade
Posts: 108
Joined: Sat 16 Aug 2008 03:51

Post by Justmade » Tue 01 Feb 2011 09:52

Thank you very much. :D

Justmade
Posts: 108
Joined: Sat 16 Aug 2008 03:51

Post by Justmade » Thu 24 Mar 2011 09:27

The auto gen script engine is done for over a month now and is working fine except I still have to manually delete the uses cause and Schema script's comment. see http://www.devart.com/forums/viewtopic.php?t=20208

Can you suggest about when can these 2 simple feature be added so that I can completely rely on your generated scripts without need to manual modification?

Thanks you again for your kind acceptance of these feature requests.

.jp
Devart Team
Posts: 345
Joined: Wed 09 Sep 2009 06:55
Location: devart

Post by .jp » Thu 24 Mar 2011 13:42

Yes, this feature is enqueued.

The point is that there are so many features our users want to have implemented, that we can not physically manage to implement all of them at once.

I asked our project manager if it is possible to include this functionality into the fifth product version that should be released in the first half of April. But he said that it was the final cycle of regression testing and that new functionality could be added only to the next version of the product (after this one). If we add one more feature to the fifth version, we'll have to postpone the release date, and we've already done this several times.

Besides, we will set priority for the first 4 or 5 features that have most user votes. If you can, please add this feature to the following resource: http://devart.uservoice.com/forums/7729 ... -for-mysql

Post Reply