Access a MySQL database
- 47 files
- 146 downloads
The submission collects several small utilities 'wrapping' Yannick Maret's 'mym' Matlab/MySQL interface, available from
http://sourceforge.net/projects/mym
Their application is illustrated by script mydemo.m, which uses the FEX download data presented in FEX submission 'A week on File Exchange'. First, we read the data (6 mixed-type columns, over 1 million rows) from a text file into a MySQL table, using 'load infile', passed through the basic mym interface. Next, we retrieve the table's structure and contents into Matlab workspace using TBATTR and TBREAD, and take the data back to MySQL with TBWRITE.
We observe that text-file-mediated exchange, accommodated on MySQL's side by 'load infile' and 'select into outfile', is a vastly superior option for large datasets; TBREAD and TBWRITE (the latter operating through multiple-row 'insert values' flushes) are more convenient for small datasets with many columns.
Cite As
Dimitri Shvorob (2020). Access a MySQL database (https://www.mathworks.com/matlabcentral/fileexchange/17897-access-a-mysql-database), MATLAB Central File Exchange. Retrieved .
Comments and Ratings (3)
Updates
| 1.0.0.0 | BSD |
MATLAB Release Compatibility
Platform Compatibility
Windows macOS LinuxCategories
Tags
Acknowledgements
Inspired by: MySQL Database Connector, Myblob, A Powerful Sidekick: Using MySQL for High-Volume Data Manipulation in Matlab, The Twain Shall Meet: Facilitating Data Exchange between SAS and Matlab, Analyze FEX download data
Inspired: MySQL shortcut files, queryMySQL
Discover Live Editor
Create scripts with code, output, and formatted text in a single executable document.
mym utilities/
mym utilities/html/
Select a Web Site
Choose a web site to get translated content where available and see local events and offers. Based on your location, we recommend that you select: .
Select web siteYou can also select a web site from the following list:
Americas
- América Latina (Español)
- Canada (English)
- United States (English)
Europe
- Belgium (English)
- Denmark (English)
- Deutschland (Deutsch)
- España (Español)
- Finland (English)
- France (Français)
- Ireland (English)
- Italia (Italiano)
- Luxembourg (English)
- Netherlands (English)
- Norway (English)
- Österreich (Deutsch)
- Portugal (English)
- Sweden (English)
- Switzerland
- United Kingdom (English)
jackstar1 (view profile)
Dadi Gudmundsson (view profile)
Overall I find this useful and good. Reason for less than perfect rating is:
1) These wrapper files tend to replace more detailed mym error messages with their own. Easy to fix.
2) For some datasets the s string created in TBWRITE line 79 ends in a comma and a space. This means that line 80 doesn't remove the comma at the end. This then gives an SQL error. Haven't figured out why some datasets do this, but not others. Pretty easy to fix.
Cheers
dadigu
Howard Bussey (view profile)
I'm trying to use a MySQL server that is on a non-standard port (not 3306) and mym doesn't connect. I can use the MySQL browser to see the databases that server manages, so I know the server is running and listening on the non-standard port. I also tried specifying port 3306 (standard) for a server with the standard configuration - that didn't connect either.
Has anyone else tried specifying a port in the connection string? Did it work for you?