1) I've configured my "config/database.xml" adapter to point
at /var/run/mysqld/mysqld.sock, which is what my mysqld specifies on the
command line. I checked, and the socket exists, and is readable and
writeabel by everyone. However, I still get the following error:
[dcorbin@bass ~/projects/app] rake
(in /home/dcorbin/projects/app)
rake aborted!
database configuration specifies nonexistent /var/run/mysqld/mysqld.sock
adapter
./Rakefile:15
Please help.
2) Is this list really the best place to get rails-specific support? I can
find no other specific list.
David
David Corbin wrote:
2) Is this list really the best place to get rails-specific support? I can find no other specific list.
There is a specific rails list you might want to try:
http://lists.rubyonrails.org/mailman/listinfo/rails
I don't know if anyone's ever made this observation before, or if it has
another well-known name:
"You always find the answer right after you post your question." -- Corbin's
Law.
Not only did I find that mailing list, but I found the IRC channel where I got
straightend out. User error in editing the config/database.yml file.
Thanks.
David
···
On Wednesday 27 April 2005 07:36 am, will wrote:
David Corbin wrote:
> 2) Is this list really the best place to get rails-specific support? I
> can find no other specific list.
There is a specific rails list you might want to try:
http://lists.rubyonrails.org/mailman/listinfo/rails
David A. Black wrote:
Hi --
David Corbin wrote:
2) Is this list really the best place to get rails-specific support? I
can find no other specific list.
There is a specific rails list you might want to try:
http://lists.rubyonrails.org/mailman/listinfo/rails
I don't know if anyone's ever made this observation before, or if it has
another well-known name:
"You always find the answer right after you post your question." -- Corbin's Law.
I don't know if it has a name (I never remember these "Law" names
anyway -- it's my anarchistic streak but it's definitely been
observed before. Google for "right after i asked the question"
This technique to find the answer is called "rubber ducking" - see Dave and Andy's book "The Pragmatic Programmer", page 95.
Happy rubying
Stephan
···
On Wed, 27 Apr 2005, David Corbin wrote:
On Wednesday 27 April 2005 07:36 am, will wrote: