On 19 November 2012 12:52, Ann Harrison <a...@qbeast.net> wrote: > > I assure you that MySQL dump produces a text file containing insert > statements. > > Best regards, > > Ann
Oh, I believe you, as I have seen them/used them, but like I said, I could not imagine anyone (implied 'reasonable') using them for large datasets. Straight sql dumps have their place in certain limited circumstances, but, using them to load or extract large data sets is like trying to use a hammer as a wrench. I have seen dump tools for oracle that did use parametrized inserts and relative paths to individual files for each hex encoded blob. The entire dump was placed into a single zip file so that you could extract/modify/delete details as needed. Something like that could be useful as a migration tool or snapshot based backups like gbak. The only benefit in comparison to gbak would be the fact that the end user would be able to easily manipulate the output/input files. As for support, if the user screws up their data/backups by hand editing the files, that is their problem. The project should not concern itself with people who are given enough rope to climb a mountain but decide to hang themselves instead. ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
