mysqldump of DB vs. individual tables

[Dan F]

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