On Wednesday 20 May 2009 14:47:18 Simone Piccardi wrote: > Anselm Lingnau wrote: > > Donald A. Tevault wrote: > >> I have to agree. I can see having an exam candidate know how to create > >> user accounts, grant privileges, etc. But, I don't understand the > >> emphasis on manipulating data tables. That should definitely be the job > >> of a database admin. > > > > I think this is the wrong way round. > > > > I'd look to a database administrator to deal with the intricacies of > > creating user accounts and setting up privileges -- after all, these even > > depend on the database system that one is using. > > Not fully convinced by this, one of the most frequent task for a > sysadmin dealing whit databases is having to install and configure a web > application that require to create a database and an user with > appropriate privileges to write on it. Nothing so complex to require a > DBA... > > So I think that creating a database, an user account and granting it > privilege access in such simple manner is a basic knowledge needed for > sysadmin.
I agree, this is pretty common. And doing it for MySQL is much more common than for Postgres, which can make formulating items tricky. > But that's right, these operation are different depending on database > system you are using, so it will be difficult to put them on a generic > test. > > > However, it turns out that these days many software packages allow things > > like logging to SQL databases rather than files. As a system > > administrator one must know how to query these logs. Similarly, there are > > SQL backends for storing user accounts or DNS resource records. Finally, > > various software packages use SQLite databases as their native file > > format (e.g., Firefox). On occasion, it is very useful to be able to > > access these files in SQL. > > That's right but most of these operation are just SELECT to read data; > in my experience the only other operation that I used sometime is UPDATE > to change some values in a table, but this far less common than needing > to create a database and give access to a dedicated user. I almost never > used JOIN, DELETE, INSERT... so I have lot of doubts covering these in > the exam. I find myself using INSERT, UPDATE, DELETE and SELECT quite a lot, mostly on simple databases that store for example usernames and passwords, or mail aliases. These commands are pretty standard across the majority of SQL databases and are analogous to how you would edit a text file, or even using useradd, usermod, userdel and id. 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. -- alan dot mckinnon at gmail dot com _______________________________________________ lpi-examdev mailing list [email protected] http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
