Sheeri K. Cabral wrote: > (see comment inline) > > On 7/16/08, Monty Taylor <[EMAIL PROTECTED]> wrote: >>> Lately to check the status of a server I find myself using mostly the >>> mysql utility w/ --html option. It's extremely easy then to document >>> 'in pretty' format what's going on in the server. My favorite command >>> lines look like: >>> >>> mysql --html -e "SHOW VARIABLES LIKE <someting>" >> >> I can _totally_ see this... however, if we shipped a utility that did >> this sort of thing, but was optimized to pull status and/or variables >> out and make HTML... would that satisfy your need? (good use case, btw) >> >> I'm hoping if we can make the library more sensible to work with >> consistently, we can make a whole bunch of little utilities without >> having to put the features all in the same place...
+1 on this. > I like this idea. I think it's trivially easy to make, say, a perl script > that takes text formatted a certain way (horizontal or vertical, tab > delimited or table formatted, with or without column headings) and make html > (or xml) for it. Then you can even just do something like > > drizzle-client -e "show variables like <something>" | dzformat.pl > > niceoutput.txt > > Oh, and with drizzle can we stop the insanity that is calling everything > "mysql"? Call the client "dzclient" or something, because "mysql" the > client vs. "mysqld" the server daemon vs "MySQL" the suite of tools is > really a pain. (mostly 'cause I'm writing a book on MySQL right now, but in > general it's a pain). I disagree with this. The general convention is to have the server suffixed with d (for daemon) and the client not suffixed. I prefer this convention. Just my two cents, Jay _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
