Michael Koziarski wrote:
That is, setting a socket is the exception rather than the rule. For
most of the get-up-and-running apps I've seen, the socket isn't
necessary. Trying to set it is often an impediment to getting
started with Rails. But I suspect there may be downsides that led to
the decision to use a default socket.
I committed the current implementation of the 'socket finder'. I
guess if all major mysql packagers (linux distros etc.) configure
mysql to listen for TCP/IP then there's no harm.
Perhaps an alternative is to have the commented version if mysql.sock
wasn't found in any of the common locations?
I vote for this option.
-- stefan
--
For rails performance tuning, see: http://railsexpress.de/blog
Subscription: http://railsexpress.de/blog/xml/rss20/feed.xml
_______________________________________________
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core
