Arvind Narayanan writes:
On Fri, Jan 02, 2004 at 04:18:39PM -0800, Toby Bartels wrote:
SQL is very useful, especially if search is off or you're searching for spelling-mistakes or HTML-tables. But SQL-Queries can cause heavy load for the server, so it would also be good to seperate sysop and sql-rights and make them depending of the user's knowledge.
That is a fair point, although it doesn't mean that we need to separate things in the MediaWiki code. Since I don't know SQL enough to use it, I don't run any SQL queries; there's no need to take SQL rights away. If another sysop only wants to run SQL queries, but not get involved in deletions or IP blocks, then that's OK too.
I agree. If someone is given sysop powers it means that we trust them to know what they don't know :)
Arvind
Yes, I agree. I think that a sysop should be responsible. If I were a sysop, and I didn't know anything about SQL, I wouldn't mess with sql queries, and I would hope that other sysops would do the same. (note, this is just hypothetical as I know about SQL and I am not a sysop.) Still, I hope that only individuals who are responsible are given powers. On the other hand, I think that individuals who aren't sysops, might become, "SIP's" (sysops in training,) and they could edit protected pages, and could not delete, or block. Using this method, we could better test if newer wikipedians will abuse sysop powers. As I said, I'm not a sysop, so I can't comment as well on the way powers work, but this is just my thought on the issue. -------------------------------------------------------------------------------- Get your free 15 Mb POP3 email @alexandria.cc Click here -> http://www.alexandria.cc/