Improvements
The following highlights a few of the more significant improvements.
* mysqldbexport, mysqldbimport, and mysqldbcopy have multiprocessing support that allows for much improved performance
* mysqlfrm can now generate a .frm file with storage engine substitution
* Mac OS X packages added!
* mysqlserverinfo now includes the log files (error, general, slow)
* mysqlprocgrep can now search and kill processes by id
* mysqlmetagrep can now search the body of routines with the new --body option
* all utilities report license type with --version and --help
* all utilities have the new --license option to view the license text
* the mysqluc now reports errors with clearer text and tags the message with the name of the utility that returned the error
* mysqlindexcheck now warns user if there is not enough information to calculate best/worst indexes
* rpm, debian, and msi packages will update/remove old versions automatically when installing a newer version
* the documentation is now a separate reference manual (see link below)
The following spotlight some of the more important enhancements.
Multiprocessing with mysqldbexport, mysqldbimport, and mysqldbcopy
The performance of the mysqldbcopy, mysqldbexport and mysqldbimport utilities has been significantly improved. Moreover, a new --multiprocess option was added to allow concurrent execution making the most of the available CPU resources (the number of CPU cores).
Note: the --thread option in mysqldbcopy was replaced by the --multiprocess option.
Multiprocessing is applied at different levels according to the operating system. The utilities mysqldbcopy and mysqldbexport allow multiprocessing at the table-level for non-Windows systems and at the database-level for Windows system. The mysqldbimport utility allows multiprocessing at the file-level independently from the OS.
Other more specific options were also added for performance reasons for the other utility. A new --output-file option was added to mysqldbexport to specify a file to store the generated output which allows faster output than sending messages to the terminal.
Two additional additional options are now available in mysqldbimport: 1) --autocommit to enable autocommit for each operation because now by default a single commit is performed at the end of importing each file which is much faster, and 2) --max-bulk-insert to adjust the maximum number of inserts in a bulk, following the improved bulk insert support that is now provided.
Create New .frm Files with New Storage Engine
The mysqlfrm utility allows you to use the --new-storage-engine and the new --frmdir option to provide a directory to store the new .frm files. This feature is useful for those who want to recover the CREATE statement from existing .frm files and change the storage engine without having to launch the server. Try it out!
Mac OS X Installer
Yes, we now have a Mac OS X package installer. If you install Utilities with this installer, you will need to either use Connector/Python version 1.1.4 or later (which has a Mac OS X installer too) or use the Connector/Python 1.0.8 or later source code package and install manually.
How Can I Download MySQL Utilities?
You can download MySQL Utilities 1.3.6 from the following link using one of the pre-built installation repositories including a source download.
http://dev.mysql.com/downloads/tools/utilities/
If you are a commercial customer, you can download MySQL Utilities from the following link:
https://edelivery.oracle.com/
MySQL Utilities is also available on Lauchpad as a source download at:
https://code.launchpad.net/mysql-utilities
Where is the Documentation?
You can find online documentation for MySQL Utilities version 1.3 at:
http://dev.mysql.com/doc/index-gui.html
Hi Chuck,
ReplyDeleteSorry for contacting you this way. I was wondering if you would be interested in reviewing http://ubiq.co for your readers. It is a new web based MySQL reporting tool I’ve built. Happy to provide extended free usage to your readers.
Regards,
Sreeram
Hi chuck
ReplyDeleteI am using arduino Yun
I got down the file.zip, later I uniz and make a dir with name Sha1 and mysql. After this I put in the files of each one. For Sha1 is ok. But for myslq.h your code for first exemple not compile,
error :
____________
Arduino:1.6.5 (Windows 7), Placa:"Arduino Yún"
sketch_dec03d.ino:4:19: fatal error: mysql.h: No such file or directory
compilation terminated.
Error de compilación
This report would have more information with
"Show verbose output during compilation"
activala desde Archivo > Preferencias
______
I do not understand, if the dir is created in Mydocuments/Arduino/Libraries
Why it says that dir does not exists? Moreover, file mysql.h is inside I checked!
I would high apreciate your help or recomendation.
Regards
oscar
Hi chuck
ReplyDeleteI am using arduino Yun
I got down the file.zip, later I uniz and make a dir with name Sha1 and mysql. After this I put in the files of each one. For Sha1 is ok. But for myslq.h your code for first exemple not compile,
error :
____________
Arduino:1.6.5 (Windows 7), Placa:"Arduino Yún"
sketch_dec03d.ino:4:19: fatal error: mysql.h: No such file or directory
compilation terminated.
Error de compilación
This report would have more information with
"Show verbose output during compilation"
activala desde Archivo > Preferencias
______
I do not understand, if the dir is created in Mydocuments/Arduino/Libraries
Why it says that dir does not exists? Moreover, file mysql.h is inside I checked!
I would high apreciate your help or recomendation.
Regards
oscar
Hi. First, this is the wrong blog to post this question, but I will answer it anyway. :)
DeleteIs it possible you copied the folders while the IDE was open? If so, you need to restart the IDE for it to "see" the new library.
You can tell it is read if there is an entry in the examples menu.
I recommend naming the folder "mysql_connector" instead of "mysql" but that just a preference. Also, make sure you are not embedding the library files in subfolders.