469,167 Members | 1,207 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,167 developers. It's quick & easy.

mysqldump of DB vs. individual tables

Folks,

I find it useful for browsing to dump each table of a DB, i.e.
psuedo-code like

foreach table
mysqldump --add-drop-table DB table > table

This produces a file per table, and that file has the DDL and data.

My question: does this per-table version capture all the information
that doing a full-DB dump (as follows) would?

mysqldump --add-drop-table DB > DB

I tested, and noticed that foreign key constraints and indexes (in my
InnoDB database) are appearing nicely in the per-table version. Is
anything missing?

I'm using mysql "Ver 12.18 Distrib 4.0.12" (I assume 4.0.12) for Linux.
Thanks for any thoughts.

Dan

--
Dan Frankowski df******@cs.umn.edu


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/my***********...ie.nctu.edu.tw

Jul 19 '05 #1
0 1624

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

reply views Thread by Dan F | last post: by
3 posts views Thread by g00g0 | last post: by
7 posts views Thread by Adam Smith | last post: by
3 posts views Thread by Christopher Mouton | last post: by
6 posts views Thread by Robert Blackwell | last post: by
6 posts views Thread by Antoni | last post: by
1 post views Thread by CARIGAR | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.