In my book, it's a tradeoff between knowing exactly what you
told the
tool to do on a command-line versus assuming what a GUI tool
is doing.
For instance MYSQL has the ability to set a collation (what
I would
have called a character set) on each table. You can do that
explicitly
in the command-line. But the designer of the GUI tool has to
play
trade-off between vomiting all the possible options on the
user and
hiding/showing them to the user based on some idea of the
user's
experience level. So if you just click the button that says
"Create
Table", unless there's some verbosity to the GUI, you
may be setting
things that you may not want. I tend to start with the
command line,
then play around with various GUI tools until I find one
that
creates/manipulates the way I want it too, then just use the
GUI.
Howard
On 1/12/07, Robert Reil <robreil motorcyclecarbs.com>
wrote:
>
>
> Granted... But what about the fact that it takes lots
of time to learn
> another way to do the same thing versus the time it
takes to just navigate
> to the click.
--
Howard Fore, howard.foregmail.com
"Gliddy glub gloopy / Nibby nabby noopy / La la la lo
lo / Sabba sibby
sabba / Nooby abba nabba / Le le lo lo / Tooby ooby walla /
Nooby abba
naba / Early morning singing song" - Good Morning
Starshine
------------------------------------------------------------
-
To unsubscribe from this list, manage your profile
http://www
.acfug.org?fa=login.edituserform
For more info, see http://www.acfug.or
g/mailinglists
Archive h
ttp://www.mail-archive.com/discussion%40acfug.org/
List hosted by http://www.fusionlink.com
------------------------------------------------------------
-
|