On Wednesday 20 May 2009 19:14:02 Anselm Lingnau wrote: > Alan McKinnon wrote: > > I agree that JOINs are too complex for LPIC-1, you need to know some > > database theory to grasp what they are all about, and that is outside the > > scope of LPI exams. > > I don't buy this. LPIC-1 candidates had to know about join(1) for just > about as long as I can remember. From there to the basic SQL JOINs that the > new exam requires doesn't exactly look like a giant leap to me.
join(1) always appears to me to be over-rated and I have no idea why it's in the objectives. The only person I've ever seen use it in real life is me - joining two log files that really should have been one all along. But having said that, yes - it is not a huge leap to go from join(1) to SQL JOIN > I've put up the chapter on SQL from our »Advanced Linux« training manual on > > http://www.linupfront.de/download/grd2-en-sql.pdf > > This contains what I consider a reasonable quick-and-dirty introduction to > SQL for LPIC-1 candidates. Feel free to look at this and send me comments. And it looks pretty good too. It does about the same job as the basic tutorial shipped with MySQL. Good job. IF (big if) there is enough time in the class schedule to cover this material, that would be good. But I've always found that exam objectives are a strict subset of what the student really needs to know to get anything done, and decent course material always covers more (you can put the extra bit in an "Advanced" section at the end of chapters if need be). Does it belong in the exam objectives though? I lean towards saying no. It's very easy to bloat the objectives so some things must be omitted. I consider SQL JOIN one of the things that can be dropped if trimming is to be done. Others may disagree, that's why LPI gets lots of input and tries to go with a sane median. -- alan dot mckinnon at gmail dot com _______________________________________________ lpi-examdev mailing list [email protected] http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
