MySQL Bugs: #22561: MySQL Query Browser Should Have An Export To Sql Option

Bug #22561	MySQL Query Browser Should Have An Export To Sql Option
Submitted:	21 Sep 2006 17:44	Modified:	27 Sep 2006 18:28
Reporter:	Bill Mill	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S4 (Feature request)
Version:	1.2.1 beta	OS:	Any (All)
Assigned to:		CPU Architecture:	Any
Tags:	export sql mysql query browser

Description:
Mysql Query Browser can export resultsets into a whole bunch of formats, but not the most useful one - a SQL insert statement. This feature would make the product 2x as useful for me.

Use cases:

1) I want to add a row to a table with many columns. Fortunately, only a few of them need changing. Instead of typing my data into each column, I just select the row most similar to the one I need to add, export as an insert, and update the relevant fields. Much faster.

2) I want to copy a small-medium number of rows from one dev database to another. It's much quicker, since I have the query browser open for both of them already, to copy the rows this way than to use mysqldump.

I'm sure there are others, it's a feature I used with Oracle extremely often, but they don't come to mind right now.

How to repeat:
Run Query Browser.

Suggested fix:
Add an "Export As Sql File" option to the "export resultset" menu.

dupe of bug #7759: http://bugs.mysql.com/bug.php?id=7759

(Sorry folks, I didn't see that the bug searcher by default doesn't search feature requests)