Harald Maaßen <har...@nwa-net.de> wrote: > I think we should add mysqldump to topic 105.3 because IMHO everybody > should be able to backup a database.
Exactly where does topic 105.3 talk about MySQL in the first place? If everybody should be able to backup a MySQL database, shouldn't everybody be able to restore one, too, so shouldn't we also add the commands to do that? Do we then also add pg_dump and pg_restore because some people may be using PostgreSQL instead? What about other SQL databases? IMHO one of the strengths of 105.3 is that so far we have managed to avoid tying it to a specific database implementation. Let's try to keep it that way. Adding mysqldump to the exam would drag in all sorts of other MySQL bits and pieces (mysqladmin? mysql?) and would expose us to criticism from people who don't like MySQL and prefer PostgreSQL, or for that matter Sqlite or DB2 or Oracle or <other popular database server of the week>. We would end up in yet another situation where we would have to include the rudiments of all of them just to avoid offending people. (We used to be in a similar place with respect to MTAs, and fortunately that has sorted itself out to some degree.) The other thing is that 105.3 is a weight-2 topic. Asking 2 questions about rudimentary SQL makes sense as far as I'm concerned; asking 2 questions about rudimentary SQL and the administration of half a dozen different SQL servers doesn't. Anselm Disclaimer: This is my own personal opinion and not that of my employer. -- Anselm Lingnau ... Linup Front GmbH ... Linux-, Open-Source- & Netz-Schulungen anselm.ling...@linupfront.de, +49(0)6151-9067-103, Fax -299, www.linupfront.de Linup Front GmbH, Postfach 100121, 64201 Darmstadt, Germany Sitz: Weiterstadt (AG Darmstadt, HRB7705), Geschäftsführer: Oliver Michel _______________________________________________ lpi-examdev mailing list lpi-examdev@lpi.org http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
