On Mon, 2003-03-10 at 22:01, Pete Harlan wrote: > On Mon, Mar 10, 2003 at 11:32:06AM -0600, Paul DuBois wrote: > > Whether it's a feature or not, it's not always so easy to figure out > > what to do. If you specify -h localhost, it can be argued that you > > really want the socket even if you specify the port. It can be > > argued conversely that if you specify the port, you should use TCP/IP > > even if you specify -h localhost. > > > > That is, if the user specifies both, it's ambiguous what the user really > > wants. > > But "localhost" is a DNS name that only happens to resolve to > 127.0.0.1. MySQL breaks this DNS abstraction by treating "localhost" > as a keyword, different from 127.0.0.1, which goes against the > principle of least surprise. (It confused me, anyway.)
This is an optimization. MySQL client makes assumption that you want to connect locally and uses fastest available way - UNIX socket. Of course, this decision can be agreed or disagreed. Tõnu --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
