Rails - Dec 2005 - Rails RC5 (0.14.4): Next stop one-oh (really, this time!)

It''s been a month since we promised that RC4 would be the final
countdown. And counting down we have. We''ve fixed a ton of major,
minor, and aesthetic issues and now have a package that we would be
very proud to call 1.0. No, it''s not completely spotless. A project of
this size with thousands of programmers using it for every application
type under the moon will never be. But it''s Pretty Damn Good.

So here it goes: Release candidate 5. This is the final, short pitstop
before 1.0 materializes next week. Thus, you''re more than well advised
to upgrade and make sure we didn''t leave anything heinous in there.
This is the "speak now or forever hold your peace" part of the
ceremony.

If you already upgraded to 0.14.x, going to RC5 is completely
effortless. Simply call upon the gems to do your bidding with: gem
install rails --include-dependencies. And you''ll be serving up your
application with all the bugs squashed. On top of that, we''ve thrown
in a new adapter for the Firebird database and added a beautiful new
index.html that''ll greet you on new applications.

So upgrade, dammit! Now. And stand by as we finish setting up the
fireworks planned for next week''s release of the long-awaited 1.0.
It''s magical times, my friends, and the spellcasting is just getting
started.
--
David Heinemeier Hansson
http://www.loudthinking.com -- Broadcasting Brain
http://www.basecamphq.com   -- Online project management
http://www.backpackit.com   -- Personal information manager
http://www.rubyonrails.com  -- Web-application framework

On 12/8/05, David Heinemeier Hansson
<david.heinemeier-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:
> It''s been a month since we promised that RC4 would be the final
> countdown. And counting down we have. We''ve fixed a ton of major,
> minor, and aesthetic issues and now have a package that we would be
> very proud to call 1.0. No, it''s not completely spotless. A
project of
> this size with thousands of programmers using it for every application
> type under the moon will never be. But it''s Pretty Damn Good.
>
> So here it goes: Release candidate 5. This is the final, short pitstop
> before 1.0 materializes next week. Thus, you''re more than well
advised
> to upgrade and make sure we didn''t leave anything heinous in
there.
> This is the "speak now or forever hold your peace" part of the
> ceremony.
>
> If you already upgraded to 0.14.x, going to RC5 is completely
> effortless. Simply call upon the gems to do your bidding with: gem
> install rails --include-dependencies. And you''ll be serving up
your
> application with all the bugs squashed. On top of that, we''ve
thrown
> in a new adapter for the Firebird database and added a beautiful new
> index.html that''ll greet you on new applications.
>
> So upgrade, dammit! Now. And stand by as we finish setting up the
> fireworks planned for next week''s release of the long-awaited 1.0.
> It''s magical times, my friends, and the spellcasting is just
getting
> started.
I upgraded to it and had some mysql connection timeout error after the
application was idle for a little bit.  Sorry for the lack of
specifics, I''ll get the exact error this evening.  I''m running
on
lighttpd/fcgi/mysql on TxD.  The application has been very stable on
0.14.3.

joevandyk wrote:
> On 12/8/05, David Heinemeier Hansson
<david.heinemeier-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>> This is the "speak now or forever hold your peace" part of
the
>> fireworks planned for next week''s release of the long-awaited
1.0.
>> It''s magical times, my friends, and the spellcasting is just
getting
>> started.
> 
> I upgraded to it and had some mysql connection timeout error after the
> application was idle for a little bit.  Sorry for the lack of
> specifics, I''ll get the exact error this evening.  I''m
running on
> lighttpd/fcgi/mysql on TxD.  The application has been very stable on
> 0.14.3.
Same problem here, made a new project:

rails MyAppli
cd MyAppli
script/generate scaffold MyModel MyController

get a error... Access denied for user: ''@localhost'' (Using
password: NO)

(root@localhost can xs database but somehow the user is empty, same 
error with edgerails...)

-- 
Posted via http://www.ruby-forum.com/.

This may be a stupid question, but after upgrading the gems do we have
to run "rails ." in our project dirs?  If that''s the case,
what exact
files do we need to overwrite?

Pat


On 12/8/05, David Heinemeier Hansson
<david.heinemeier-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:
> It''s been a month since we promised that RC4 would be the final
> countdown. And counting down we have. We''ve fixed a ton of major,
> minor, and aesthetic issues and now have a package that we would be
> very proud to call 1.0. No, it''s not completely spotless. A
project of
> this size with thousands of programmers using it for every application
> type under the moon will never be. But it''s Pretty Damn Good.
>
> So here it goes: Release candidate 5. This is the final, short pitstop
> before 1.0 materializes next week. Thus, you''re more than well
advised
> to upgrade and make sure we didn''t leave anything heinous in
there.
> This is the "speak now or forever hold your peace" part of the
> ceremony.
>
> If you already upgraded to 0.14.x, going to RC5 is completely
> effortless. Simply call upon the gems to do your bidding with: gem
> install rails --include-dependencies. And you''ll be serving up
your
> application with all the bugs squashed. On top of that, we''ve
thrown
> in a new adapter for the Firebird database and added a beautiful new
> index.html that''ll greet you on new applications.
>
> So upgrade, dammit! Now. And stand by as we finish setting up the
> fireworks planned for next week''s release of the long-awaited 1.0.
> It''s magical times, my friends, and the spellcasting is just
getting
> started.
> --
> David Heinemeier Hansson
> http://www.loudthinking.com -- Broadcasting Brain
> http://www.basecamphq.com   -- Online project management
> http://www.backpackit.com   -- Personal information manager
> http://www.rubyonrails.com  -- Web-application framework
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
>

On 12/8/05, abou ihsaan
<abouihsaan-U5wbzIpkoVrQT0dZR+AlfA@public.gmane.org>
wrote:
> joevandyk wrote:
> > On 12/8/05, David Heinemeier Hansson
<david.heinemeier-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> >> This is the "speak now or forever hold your peace" part
of the
> >> fireworks planned for next week''s release of the
long-awaited 1.0.
> >> It''s magical times, my friends, and the spellcasting is
just getting
> >> started.
> >
> > I upgraded to it and had some mysql connection timeout error after the
> > application was idle for a little bit.  Sorry for the lack of
> > specifics, I''ll get the exact error this evening. 
I''m running on
> > lighttpd/fcgi/mysql on TxD.  The application has been very stable on
> > 0.14.3.
>
> Same problem here, made a new project:
>
> rails MyAppli
> cd MyAppli
> script/generate scaffold MyModel MyController
>
> get a error... Access denied for user: ''@localhost''
(Using password: NO)
>
> (root@localhost can xs database but somehow the user is empty, same
> error with edgerails...)
That wasn''t the error I got, I believe.  Again, I''ll post it
this evening.

On 12/8/05, Pat Maddox <pergesu-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:
> This may be a stupid question, but after upgrading the gems do we have
> to run "rails ." in our project dirs?  If that''s the
case, what exact
> files do we need to overwrite?
I don''t think you need to run ''rails .''
> On 12/8/05, David Heinemeier Hansson
<david.heinemeier-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> > It''s been a month since we promised that RC4 would be the
final
> > countdown. And counting down we have. We''ve fixed a ton of
major,
> > minor, and aesthetic issues and now have a package that we would be
> > very proud to call 1.0. No, it''s not completely spotless. A
project of
> > this size with thousands of programmers using it for every application
> > type under the moon will never be. But it''s Pretty Damn Good.
> >
> > So here it goes: Release candidate 5. This is the final, short pitstop
> > before 1.0 materializes next week. Thus, you''re more than
well advised
> > to upgrade and make sure we didn''t leave anything heinous in
there.
> > This is the "speak now or forever hold your peace" part of
the
> > ceremony.
> >
> > If you already upgraded to 0.14.x, going to RC5 is completely
> > effortless. Simply call upon the gems to do your bidding with: gem
> > install rails --include-dependencies. And you''ll be serving
up your
> > application with all the bugs squashed. On top of that, we''ve
thrown
> > in a new adapter for the Firebird database and added a beautiful new
> > index.html that''ll greet you on new applications.
> >
> > So upgrade, dammit! Now. And stand by as we finish setting up the
> > fireworks planned for next week''s release of the long-awaited
1.0.
> > It''s magical times, my friends, and the spellcasting is just
getting
> > started.
> > --
> > David Heinemeier Hansson
> > http://www.loudthinking.com -- Broadcasting Brain
> > http://www.basecamphq.com   -- Online project management
> > http://www.backpackit.com   -- Personal information manager
> > http://www.rubyonrails.com  -- Web-application framework
> > _______________________________________________
> > Rails mailing list
> > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> > http://lists.rubyonrails.org/mailman/listinfo/rails
> >
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
>

> Same problem here, made a new project:
>
> rails MyAppli
> cd MyAppli
> script/generate scaffold MyModel MyController
>
> get a error... Access denied for user: ''@localhost''
(Using password: NO)
>
> (root@localhost can xs database but somehow the user is empty, same
> error with edgerails...)
Did you edit the database.yml file?

--
rick
http://techno-weenie.net

On 12/8/05, Joe Van Dyk
<joevandyk-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:
> On 12/8/05, Pat Maddox
<pergesu-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> > This may be a stupid question, but after upgrading the gems do we have
> > to run "rails ." in our project dirs?  If that''s
the case, what exact
> > files do we need to overwrite?
>
> I don''t think you need to run ''rails .''
Everything points to libraries in Railties now.  Since there haven''t
been any new scripts in script/, you don''t have to run rails.

However, you may want to run rake update_javascripts to get the latest
prototype/scriptaculous files.

--
rick
http://techno-weenie.net

solved it by upgrading from 4.0 to 4.1...

abouihsaan wrote:
> having some problems here, I did the following...
> 
> rails MyAppli
> cd MyAppli
> script/generate scaffold MyModel MyController
> 
> get a error... Access denied for user: ''@localhost''
(Using password:
> NO)
> 
> (root@localhost can xs database but somehow the user is empty, same
> error with edgerails...)
> 
> (the same thing works when I do it on 0.14.3)
> 
> David Heinemeier Hansson schreef:

-- 
Posted via http://www.ruby-forum.com/.

Is there something similar to PHP''s phpinfo() where all Rails''
version info can be dumped, to be
sure what versions are being used?

thanks
csn

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

On 12/8/05, CSN
<cool_screen_name90001-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
wrote:
> Is there something similar to PHP''s phpinfo() where all
Rails'' version info can be dumped, to be
> sure what versions are being used?
>
> thanks
> csn
The new index page has it.  Click the link and it blinds down.

--
rick
http://techno-weenie.net

On 12/8/05, Rick Olson
<technoweenie-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:
> On 12/8/05, CSN
<cool_screen_name90001-/E1597aS9LQAvxtiuMwx3w@public.gmane.org> wrote:
> > Is there something similar to PHP''s phpinfo() where all
Rails'' version info can be dumped, to be
> > sure what versions are being used?
> >
> > thanks
> > csn
>
> The new index page has it.  Click the link and it blinds down.
Would someone mind posting this new index page?

> Would someone mind posting this new index page?
Just create a new app, run script/server, and go to http://localhost:3000/

The weblog has a screenshot of it:
http://weblog.rubyonrails.com/articles/2005/12/08/rails-rc5-0-14-4-next-stop-one-oh-really-this-time



--
rick
http://techno-weenie.net

You can also do

$ cd <your-rails-app>
$ ./script/about

Kent.

On Thursday 08 December 2005 15:06, CSN wrote:
> Is there something similar to PHP''s phpinfo() where all
Rails'' version info
> can be dumped, to be sure what versions are being used?
>
> thanks
> csn
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails

The index page in /public? I''m under the impression that it
won''t be updated unless ''rails'' is
run, which apparently isn''t necessary. I''m looking for
something like <%= debug(version) %>.

csn


--- Rick Olson <technoweenie-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:
> On 12/8/05, CSN
<cool_screen_name90001-/E1597aS9LQAvxtiuMwx3w@public.gmane.org> wrote:
> > Is there something similar to PHP''s phpinfo() where all
Rails'' version info can be dumped, to
> be
> > sure what versions are being used?
> >
> > thanks
> > csn
> 
> The new index page has it.  Click the link and it blinds down.
> 
> --
> rick
> http://techno-weenie.net
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
> 

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

CSN wrote:
> The index page in /public? I''m under the impression that it
won''t be updated unless ''rails'' is
> run, which apparently isn''t necessary. I''m looking for
something like <%= debug(version) %>.
CSN,

PLEASE fix your MUA.  Every time you reply you''re creating a new
thread.
   You''ve scattered a single thread into 3 or 4 threads.

Thanks,
Steve

> PLEASE fix your MUA.  Every time you reply you''re creating a new
thread.
>    You''ve scattered a single thread into 3 or 4 threads.

not in gmail :)  Okay its in 2 threads, but I think that might be from
the ruby forum?



--
rick
http://techno-weenie.net

Rick Olson wrote:
>> PLEASE fix your MUA.  Every time you reply you''re creating a
new thread.
> 
> not in gmail :)  Okay its in 2 threads, but I think that might be from
> the ruby forum?
I think gmail threads on Subject:.  And it''s probably not from the
forum
- it''s smart about References: headers.

Regardless, please be aware of what you''re doing to the list when you
post.

Thanks for your participation, consideration, and understanding.

Sincerely,
Steve

Looks fine to me. On ruby-forum.com too. Tell it to Yahoo and/or fix your MUA...

csn


--- Stephen Waits <steve-g8GSkY9QmIteoWH0uzbU5w@public.gmane.org> wrote:
> CSN wrote:
> > The index page in /public? I''m under the impression that it
won''t be updated unless ''rails'' is
> > run, which apparently isn''t necessary. I''m looking
for something like <%= debug(version) %>.
> 
> CSN,
> 
> PLEASE fix your MUA.  Every time you reply you''re creating a new
thread.
>    You''ve scattered a single thread into 3 or 4 threads.
> 
> Thanks,
> Steve
> 
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
> 

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

CSN wrote:
> Looks fine to me. On ruby-forum.com too. Tell it to Yahoo and/or fix your
MUA...
Umm.. ok.  Since you see it perfectly it''s *obviously* my problem.  I 
apologize for the mistake.

--Steve

I got an Application Failed to start after "rake update_javascripts"
on a
Typo install, but restarting Apache fixed it.
Ernie

On 12/8/05, abou ihsaan
<abouihsaan-U5wbzIpkoVrQT0dZR+AlfA@public.gmane.org>
wrote:
>
> joevandyk wrote:
> >
> > I upgraded to it and had some mysql connection timeout error after the
> > application was idle for a little bit.  Sorry for the lack of
> > specifics, I''ll get the exact error this evening. 
I''m running on
> > lighttpd/fcgi/mysql on TxD.  The application has been very stable on
> > 0.14.3.
>
> Same problem here, made a new project:
>
> rails MyAppli
> cd MyAppli
> script/generate scaffold MyModel MyController
>
> get a error... Access denied for user: ''@localhost''
(Using password: NO)
>
> (root@localhost can xs database but somehow the user is empty, same
> error with edgerails...)
>
> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
>

_______________________________________________
Rails mailing list
Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
http://lists.rubyonrails.org/mailman/listinfo/rails

I didn''t mean to be so flip. But I don''t see what the problem
is, or how I caused it. The subject
for this thread has gotten pretty mangled - re''s before after [Rails]
or [ANN] and the line
getting truncated. Despite that, ruby-forum.com and gmail don''t appear
to have a problem keeping
all the messages together in one thread. Also, since I''m using Yahoo
Mail, I don''t know what I can
"fix".

csn


--- Stephen Waits <steve-g8GSkY9QmIteoWH0uzbU5w@public.gmane.org> wrote:
> CSN wrote:
> > Looks fine to me. On ruby-forum.com too. Tell it to Yahoo and/or fix
your MUA...
> 
> Umm.. ok.  Since you see it perfectly it''s *obviously* my problem.
I
> apologize for the mistake.
> 
> --Steve
> 
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
> 

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

On 08/12/05, David Heinemeier Hansson
<david.heinemeier-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:
> It''s been a month since we promised that RC4 would be the final
> countdown. And counting down we have. We''ve fixed a ton of major,
> minor, and aesthetic issues and now have a package that we would be
> very proud to call 1.0. No, it''s not completely spotless. A
project of
> this size with thousands of programmers using it for every application
> type under the moon will never be. But it''s Pretty Damn Good.
The version of Transaction::Simple bundled with ActiveRecord in the
lib/.../vendor directory is badly out of date and should either (a) be
removed, (b) updated, or (c) further qualified in namespace. It is my
opinion that because removal is the better option, because it will
allow the update of Transaction::Simple separately from ActiveRecord.
New features have been added to Transaction::Simple that are required
by PDF::Writer, and the version of ActiveRecord included by
Transaction::Simple conflicts with this. I have seen reports that the
removal of the vendor version of Transaction::Simple and using the
RubyGems installed or putting a new version (which is multiple files,
now) in vendor are both acceptable.

I do not plan on changing the interface of Transaction::Simple from
what is present except through addition, although I may be changing
the implementation as I understand what may be possible moving forward
to reduce object graph overload and simplify object handling that I
have discovered in PDF::Writer.

-austin
--
Austin Ziegler * halostatue-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
               * Alternate: austin-/yODNl0JVVCozMbzO90S/Q@public.gmane.org

Stephen Waits wrote:
> CSN wrote:
> 
>> The index page in /public? I''m under the impression that it
won''t be
>> updated unless ''rails'' is
>> run, which apparently isn''t necessary. I''m looking
for something like
>> <%= debug(version) %>.
> 
> 
> CSN,
> 
> PLEASE fix your MUA.  Every time you reply you''re creating a new
thread.
>   You''ve scattered a single thread into 3 or 4 threads.
That''s an exaggeration, unless your copy of Thunderbird is behaving a 
lot worse than mine. I see one split of the thread, at the point you 
were complaining about, and I can''t see the difference in
CSN''s message
headers between the messages that appear as threaded and the one that 
appeared as the start of a new thread. The ''offending'' message
had an
In-Reply-To: header with the correct message ID.

What''s your analysis? I''m inclined to blame *my* MUA.

regards

   Justin

Hi,

2005/12/8, Rick Olson
<technoweenie-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>:
> > Same problem here, made a new project:
> >
> > rails MyAppli
> > cd MyAppli
> > script/generate scaffold MyModel MyController
> >
> > get a error... Access denied for user: ''@localhost''
(Using password: NO)
> >
> > (root@localhost can xs database but somehow the user is empty, same
> > error with edgerails...)
>
> Did you edit the database.yml file?
Same problem here in my win-dev-version. I have mysql 4.0.25 and get the error
  Mysql::Error (Access denied for user: ''@localhost'' to
database ''@''):.....
I can''t easily upgrade to MySQL 4.1, because on the server is running
4.0.x too.

I didn''t change the database.yml-file.

On creating a new project, I looked into the database.yml-file, where
is a comment
# MySQL (default setup).  Versions 4.1 and 5.0 are recommended.

But that can''t be true, can it?

Greetings,
Beate

Beate Paland wrote:
> Hi,
> 
> 2005/12/8, Rick Olson
<technoweenie-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>:
> 
>>>Same problem here, made a new project:
>>>
>>>rails MyAppli
>>>cd MyAppli
>>>script/generate scaffold MyModel MyController
>>>
>>>get a error... Access denied for user:
''@localhost'' (Using password: NO)
>>>
>>>(root@localhost can xs database but somehow the user is empty, same
>>>error with edgerails...)
>>
>>Did you edit the database.yml file?
> 
> 
> Same problem here in my win-dev-version. I have mysql 4.0.25 and get the
error
>   Mysql::Error (Access denied for user: ''@localhost'' to
database ''@''):.....
> I can''t easily upgrade to MySQL 4.1, because on the server is
running 4.0.x too.
> 
> I didn''t change the database.yml-file.
> 
> On creating a new project, I looked into the database.yml-file, where
> is a comment
> # MySQL (default setup).  Versions 4.1 and 5.0 are recommended.
> 
> But that can''t be true, can it?
> 
> Greetings,
> Beate
I also see this with MySQL 4.0.13 on Windows XP:

ruby script/generate scaffold Monkey
       exists  app/controllers/
       exists  app/helpers/
       create  app/views/monkeys
       exists  test/functional/
   dependency  model
       exists    app/models/
       exists    test/unit/
       exists    test/fixtures/
       create    app/models/monkey.rb
       create    test/unit/monkey_test.rb
       create    test/fixtures/monkeys.yml
Unknown database ''@''

In script\console:

C:\radrails_0.5.1\workspace\Test>ruby script\console
Loading development environment.
 >> m = Monkey.new
Mysql::Error: Unknown database ''''
         from 
c:/ruby/lib/ruby/gems/1.8/gems/activerecord-1.13.1/lib/active_recor
d/vendor/mysql.rb:510:in `read''
         from 
c:/ruby/lib/ruby/gems/1.8/gems/activerecord-1.13.1/lib/active_recor
d/vendor/mysql.rb:152:in `real_connect''
         from 
c:/ruby/lib/ruby/gems/1.8/gems/activerecord-1.13.1/lib/active_recor
d/connection_adapters/mysql_adapter.rb:45:in `mysql_connection''
         from 
c:/ruby/lib/ruby/gems/1.8/gems/activerecord-1.13.1/lib/active_recor
d/connection_adapters/abstract/connection_specification.rb:145:in
`send''
         from 
c:/ruby/lib/ruby/gems/1.8/gems/activerecord-1.13.1/lib/active_recor
d/connection_adapters/abstract/connection_specification.rb:145:in 
`connection_wi
thout_query_cache=''
         from 
c:/ruby/lib/ruby/gems/1.8/gems/activerecord-1.13.1/lib/active_recor
d/query_cache.rb:54:in `connection=''
         from 
c:/ruby/lib/ruby/gems/1.8/gems/activerecord-1.13.1/lib/active_recor
d/connection_adapters/abstract/connection_specification.rb:106:in 
`retrieve_conn
ection''
         from 
c:/ruby/lib/ruby/gems/1.8/gems/activerecord-1.13.1/lib/active_recor
d/connection_adapters/abstract/connection_specification.rb:20:in 
`connection''
         from 
c:/ruby/lib/ruby/gems/1.8/gems/activerecord-1.13.1/lib/active_recor
d/base.rb:734:in `columns''
         from 
c:/ruby/lib/ruby/gems/1.8/gems/activerecord-1.13.1/lib/active_recor
d/base.rb:1663:in `attributes_from_column_definition''
         from 
c:/ruby/lib/ruby/gems/1.8/gems/activerecord-1.13.1/lib/active_recor
d/base.rb:1185:in `initialize_without_callbacks''
         from 
c:/ruby/lib/ruby/gems/1.8/gems/activerecord-1.13.1/lib/active_recor
d/callbacks.rb:236:in `initialize''
         from (irb):1:in `new''
         from (irb):1

Doing the same on another XP machine, with MySQL 4.1, was fine.

regards

   Justin

Yes. But it can''t be the answer to upgrade to mysql 4.1. That would
cause too much trouble. I know lots of applications (in php or so)
which have problems under 4.1, so not everybody can easily upgrade
his/her server to 4.1.

Perhaps a downgrade with ActiveRecord may help?

Beate

I''ve run across a problem.  My host installed the new gems, so my  
production application got pushed to 14.4.

After fixing one small startup glitch, all seemed well - everything  
seems to work.  But now I am getting what looks like a MySql  
connection error (error text below).  I use the utf-8 hack where the  
connection needs to ''SET NAMES UTF8'' for every connection (as
discussed here on the list).  Worked fine for months.

It looks like after running fine for a while, something happens (runs  
out of connections?) and throws the error.  If I restart the server  
(lighty), all works again.  But I have no doubt I will see the  
problem again.

Ideas?

NoMethodError (undefined method `[]'' for nil:NilClass):
     /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.13.1/lib/ 
active_record/connection_adapters/mysql_adapter.rb:322:in `connect''
     /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.13.1/lib/ 
active_record/connection_adapters/mysql_adapter.rb:174:in `reconnect!''
     /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.13.1/lib/ 
active_record/connection_adapters/abstract/ 
connection_specification.rb:103:in `retrieve_connection''
     /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.13.1/lib/ 
active_record/connection_adapters/abstract/ 
connection_specification.rb:20:in `connection''
     /lib/utf8.rb:12:in `configure_charsets''
     /lib/utf8.rb:11:in `suppress''
     /lib/utf8.rb:11:in `configure_charsets''
     /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.11.1/lib/ 
action_controller/filters.rb:354:in `send''
     /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.11.1/lib/ 
action_controller/filters.rb:354:in `call_filters''
     /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.11.1/lib/ 
action_controller/filters.rb:350:in `each''
     /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.11.1/lib/ 
action_controller/filters.rb:350:in `call_filters''
     /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.11.1/lib/ 
action_controller/filters.rb:339:in `before_action''
     /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.11.1/lib/ 
action_controller/filters.rb:331:in `perform_action_without_benchmark''
     /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.11.1/lib/ 
action_controller/benchmarking.rb:69:in `perform_action_without_rescue''
     /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.11.1/lib/ 
action_controller/benchmarking.rb:69:in `measure''
     /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.11.1/lib/ 
action_controller/benchmarking.rb:69:in `perform_action_without_rescue''
     /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.11.1/lib/ 
action_controller/rescue.rb:82:in `perform_action''
     /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.11.1/lib/ 
action_controller/base.rb:369:in `send''
     /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.11.1/lib/ 
action_controller/base.rb:369:in  
`process_without_session_management_support''
     /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.11.1/lib/ 
action_controller/session_management.rb:116:in `process''
     /usr/local/lib/ruby/gems/1.8/gems/rails-0.14.4/lib/dispatcher.rb: 
38:in `dispatch''
     /usr/local/lib/ruby/gems/1.8/gems/rails-0.14.4/lib/ 
fcgi_handler.rb:141:in `process_request''
     /usr/local/lib/ruby/gems/1.8/gems/rails-0.14.4/lib/ 
fcgi_handler.rb:53:in `process!''
     /usr/local/lib/ruby/gems/1.8/gems/rails-0.14.4/lib/ 
fcgi_handler.rb:52:in `each_cgi''
     /usr/local/lib/ruby/gems/1.8/gems/fcgi-0.8.6.1/./fcgi.rb:597:in  
`each''
     /usr/local/lib/ruby/gems/1.8/gems/fcgi-0.8.6.1/./fcgi.rb:597:in  
`each_cgi''
     /usr/local/lib/ruby/gems/1.8/gems/rails-0.14.4/lib/ 
fcgi_handler.rb:52:in `process!''
     /usr/local/lib/ruby/gems/1.8/gems/rails-0.14.4/lib/ 
fcgi_handler.rb:22:in `process!''
     /public/dispatch.fcgi:24

you can determine whether you have run out of connections by running

    mysqladmin.exe -u root -p extended

and checking ''Threads_connected,''

| Threads_connected          | 3        |
| Threads_created            | 3        |
| Threads_running            | 1        |

Then compare ''Threads_connected'' with
''max_connections'' by
doing a ''show variables;'' so that you see something like this:

...
| max_connect_errors              | 10
| max_connections                 | 50
| max_delayed_threads             | 20
...

If ''Threads_connected'' is at or close to
''max_connections'' then reset
''wait_timeout'' in the my.ini file to something like 30 so that
the
connections are automatically reused after 30 seconds of inactivity.

   wait_timeout=30

The default wait_timeout is 8 hours, which means a connection will
not be recycled for 8 hours after it was last used unless it is
explicitly closed.




Brett Walker wrote:
> I''ve run across a problem.  My host installed the new gems, so my
> production application got pushed to 14.4.
> 
> After fixing one small startup glitch, all seemed well - everything  
> seems to work.  But now I am getting what looks like a MySql  connection 
> error (error text below).  I use the utf-8 hack where the  connection 
> needs to ''SET NAMES UTF8'' for every connection (as 
discussed here on
> the list).  Worked fine for months.
> 
> It looks like after running fine for a while, something happens (runs  
> out of connections?) and throws the error.  If I restart the server  
> (lighty), all works again.  But I have no doubt I will see the  problem 
> again.
> 
> Ideas?
[snip]

Beate Paland wrote:
> Yes. But it can''t be the answer to upgrade to mysql 4.1. That
would
> cause too much trouble. I know lots of applications (in php or so)
> which have problems under 4.1, so not everybody can easily upgrade
> his/her server to 4.1.
I mentioned that the same thing worked with 4.1 as evidence that I was 
trying to do the right thing with 4.0, not as a suggestion that you 
should upgrade. Sorry if I gave that impression.
> 
> Perhaps a downgrade with ActiveRecord may help?
Looking at where the exception occurs, the file

   activerecord-1.13.1\lib\active_record\vendor\mysql.rb

appears to be the pure ruby mysql driver. Looking at the log comments in 
SVN, it has local patches by the Rails team.

 From the Rails MySQL adapter code, it appears that this local copy will 
only be used if no other MySQL driver is present.

In the previous version of ActiveRecord, there were mysql.rb and 
mysql411.rb files, which were both loaded.

Renaming the mysql.rb file in 
activerecord-1.13.1\lib\active_record\vendor and copying across the 
previous version allows me to connect to the database, but might 
introduce other problems... I should really look into how to run the 
ActiveRecord unit tests.

You could give it a try, and I''m mentioning this in the hope that it 
will help the Rails team to home in on the problem and produce a proper fix.

regards

   Justin

Lou, thanks.  I will monitor the connections throughout the day and  
see what happens.  Currently the max_connections are 128, and the  
threads are at 16.  The wait_timeout is 600 (my guess is I can''t  
tweak that value on TextDrive).

I still think this might point to a potential issue with 14.4, as  
this behavior didn''t start occurring until the upgrade.

I will monitor and see what happens.

Thanks,
Brett

On Dec 9, 2005, at 9:06 AM, Lou Vanek wrote:
> you can determine whether you have run out of connections by running
>
>    mysqladmin.exe -u root -p extended
>
> and checking ''Threads_connected,''
>
> | Threads_connected          | 3        |
> | Threads_created            | 3        |
> | Threads_running            | 1        |
>
> Then compare ''Threads_connected'' with
''max_connections'' by
> doing a ''show variables;'' so that you see something like
this:
>
> ...
> | max_connect_errors              | 10
> | max_connections                 | 50
> | max_delayed_threads             | 20
> ...
>
> If ''Threads_connected'' is at or close to
''max_connections'' then reset
> ''wait_timeout'' in the my.ini file to something like 30 so
that the
> connections are automatically reused after 30 seconds of inactivity.
>
>   wait_timeout=30
>
> The default wait_timeout is 8 hours, which means a connection will
> not be recycled for 8 hours after it was last used unless it is
> explicitly closed.
>
>
>
>
> Brett Walker wrote:
>
>> I''ve run across a problem.  My host installed the new gems, so
my
>> production application got pushed to 14.4.
>> After fixing one small startup glitch, all seemed well -  
>> everything  seems to work.  But now I am getting what looks like a  
>> MySql  connection error (error text below).  I use the utf-8 hack  
>> where the  connection needs to ''SET NAMES UTF8'' for
every
>> connection (as  discussed here on the list).  Worked fine for months.
>> It looks like after running fine for a while, something happens  
>> (runs  out of connections?) and throws the error.  If I restart  
>> the server  (lighty), all works again.  But I have no doubt I will  
>> see the  problem again.
>> Ideas?
> [snip]
>
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails

On 12/9/05, Brett Walker <walkerbl-O5WfVfzUwx8@public.gmane.org>
wrote:
> I''ve run across a problem.  My host installed the new gems, so my
> production application got pushed to 14.4.
>
> After fixing one small startup glitch, all seemed well - everything
> seems to work.  But now I am getting what looks like a MySql
> connection error (error text below).  I use the utf-8 hack where the
> connection needs to ''SET NAMES UTF8'' for every connection
(as
> discussed here on the list).  Worked fine for months.
>
> It looks like after running fine for a while, something happens (runs
> out of connections?) and throws the error.  If I restart the server
> (lighty), all works again.  But I have no doubt I will see the
> problem again.
>
> Ideas?
>
> NoMethodError (undefined method `[]'' for nil:NilClass):
>      /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.13.1/lib/
I believe this is the error I got as well (running on TxD with mysql
and on 0.14.4).  I didn''t go home last night, so didn''t get a
chance
to try it out.

Joe

Works great on FireFox, but not on Safari 2.0.2.  On Safari, it  
doesn''t drop down at all, just sits there.

Brett

On Dec 8, 2005, at 2:21 PM, Rick Olson wrote:
>> Would someone mind posting this new index page?
>
> Just create a new app, run script/server, and go to http:// 
> localhost:3000/
>
> The weblog has a screenshot of it:
> http://weblog.rubyonrails.com/articles/2005/12/08/rails-rc5-0-14-4- 
> next-stop-one-oh-really-this-time
>
>
>
> --
> rick
> http://techno-weenie.net
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails

The error is definitely still occurring for me - it''s happened 3  
times since this morning.

It might be a database connection timeout like Joe mentioned.   
Looking that the logs, it seems like the error occurs after a period  
of inactivity (usually over 10 minutes).  The connection timeout at  
TxD is 10 minutes, so this fits.

Is it time to open a ticket on this?

Brett

On Dec 9, 2005, at 11:45 AM, Joe Van Dyk wrote:
> On 12/9/05, Brett Walker <walkerbl-O5WfVfzUwx8@public.gmane.org>
wrote:
>> I''ve run across a problem.  My host installed the new gems, so
my
>> production application got pushed to 14.4.
>>
>> After fixing one small startup glitch, all seemed well - everything
>> seems to work.  But now I am getting what looks like a MySql
>> connection error (error text below).  I use the utf-8 hack where the
>> connection needs to ''SET NAMES UTF8'' for every
connection (as
>> discussed here on the list).  Worked fine for months.
>>
>> It looks like after running fine for a while, something happens (runs
>> out of connections?) and throws the error.  If I restart the server
>> (lighty), all works again.  But I have no doubt I will see the
>> problem again.
>>
>> Ideas?
>>
>> NoMethodError (undefined method `[]'' for nil:NilClass):
>>      /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.13.1/lib/
>
> I believe this is the error I got as well (running on TxD with mysql
> and on 0.14.4).  I didn''t go home last night, so didn''t
get a chance
> to try it out.
>
> Joe
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Beate Paland wrote:
> Yes. But it can''t be the answer to upgrade to mysql 4.1. That
would
> cause too much trouble. I know lots of applications (in php or so)
> which have problems under 4.1, so not everybody can easily upgrade
> his/her server to 4.1.
Use the C bindings:
   gem install mysql


On Dec 9, 2005, at 7:17 AM, Justin Forder wrote:
> You could give it a try, and I''m mentioning this in the hope that
> it will help the Rails team to home in on the problem and produce a  
> proper fix.
At this point, barring a bug in the AR adapter, it''s up to the MySQL  
driver developers.  The updated mysql driver that has replaced the  
old driver + mysql411 is more compatible, but clearly isn''t good
enough.

Use the C bindings.

jeremy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (Darwin)

iD8DBQFDmeERAQHALep9HFYRAldIAKCpQ4P3rtLd/KYdchNgKm2PvoiqogCfWVYc
ixf39HSmiVk36DlhN6FZFp4=dTcI
-----END PGP SIGNATURE-----

On 12/9/05, Jeremy Kemper <jeremy-w7CzD/W5Ocjk1uMJSBkQmQ@public.gmane.org>
wrote:


-----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Beate Paland wrote:
> > Yes. But it can''t be the answer to upgrade to mysql 4.1. That
would
> > cause too much trouble. I know lots of applications (in php or so)
> > which have problems under 4.1, so not everybody can easily upgrade
> > his/her server to 4.1.
>
> Use the C bindings:
>    gem install mysql


That may not be an option for everyone.  Are there other options, or is
MySQL + Rails now a doubtful choice?


James


_______________________________________________
Rails mailing list
Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
http://lists.rubyonrails.org/mailman/listinfo/rails

It seems there is a problem with pure Ruby version of Mysql driver that comes 
with 0.14.4. I''ve opened a ticket

http://dev.rubyonrails.org/ticket/3160

Kent.

On Friday 09 December 2005 15:04, ruby doc wrote:
> On 12/9/05, Jeremy Kemper
<jeremy-w7CzD/W5Ocjk1uMJSBkQmQ@public.gmane.org> wrote:
>
>
> -----BEGIN PGP SIGNED MESSAGE-----
>
> > Hash: SHA1
> >
> > Beate Paland wrote:
> > > Yes. But it can''t be the answer to upgrade to mysql 4.1.
That would
> > > cause too much trouble. I know lots of applications (in php or
so)
> > > which have problems under 4.1, so not everybody can easily
upgrade
> > > his/her server to 4.1.
> >
> > Use the C bindings:
> >    gem install mysql
>
> That may not be an option for everyone.  Are there other options, or is
> MySQL + Rails now a doubtful choice?
>
>
> James

David Heinemeier Hansson wrote:
>It''s been a month since we promised that RC4 would be the final
>countdown. And counting down we have. We''ve fixed a ton of major,
>minor, and aesthetic issues and now have a package that we would be
>very proud to call 1.0. No, it''s not completely spotless. A project
of
>this size with thousands of programmers using it for every application
>type under the moon will never be. But it''s Pretty Damn Good.
>  
>
[snip]

"pragdave", et. al. -- is there a corresponding update to "Agile
Web
Development with Rails" in the works? Those gerbils must be chomping at 
the bit to build me a copy. :)

-- 
M. Edward (Ed) Borasky

http://linuxcapacityplanning.com

Jeremy Kemper wrote:
> Beate Paland wrote:
> 
>> Yes. But it can''t be the answer to upgrade to mysql 4.1. That
would
>> cause too much trouble. I know lots of applications (in php or so)
>> which have problems under 4.1, so not everybody can easily upgrade
>> his/her server to 4.1.
> 
> 
> Use the C bindings:
>   gem install mysql
> 
> 
> On Dec 9, 2005, at 7:17 AM, Justin Forder wrote:
> 
>> You could give it a try, and I''m mentioning this in the hope
that  it
>> will help the Rails team to home in on the problem and produce a  
>> proper fix.
> 
> 
> At this point, barring a bug in the AR adapter, it''s up to the
MySQL
> driver developers.  The updated mysql driver that has replaced the  old 
> driver + mysql411 is more compatible, but clearly isn''t good
enough.
> 
> Use the C bindings.
> 
> jeremy
The problem in connecting is not in the AR adapter (I have checked the 
parameters being passed in to the real_connect call) - it happens within 
the real_connect method of the mysql.rb driver.

Looking harder at this, it is clear that the problem is not with the 
driver in its original form (version 0.2.6) from

   http://www.tmtm.org/en/ruby/mysql/README_en.html

but with the patch applied to it to make it work with MySQL 4.1.1 and above.

Whereas the mysql411.rb overlay that you used in the previous release 
candidate did a check based on the MySQL version string, the patch looks 
at flags in the @server_capabilities. The flags themselves look 
sensible; for me, on first connection to MySQL 4.0.13, they are:

   Server capabilities: 8236
   Long password: false
   Found rows: false
   Long flag: true
   Connect with db: true
   No schema: false
   Compress: true
   ODBC: false
   Local files: false
   Ignore space: false
   Protocol 41: false
   Interactive: false
   SSL: false
   Ignore SIGPIPE: false
   Transactions: true
   Reserved: false
   Secure connection: false

but the way they are being used to switch between old and new (4.1.1+) 
behaviour is totally broken:

   CLIENT_PROTOCOL_41  = 1 << 9
   ...
   CLIENT_SECURE_CONNECTION  = 1 << 15
   ...
   PROTO_AUTH41 = CLIENT_PROTOCOL_41 | CLIENT_SECURE_CONNECTION
   ...
     if !@server_capabilities & PROTO_AUTH41  # ***** !!!!!
       # old behaviour
     else
       # new behaviour
     end

This broken condition (which always evaluates to false, because 
@server_capabilities is a Fixnum, so !@server_capabilities is false) 
appears in lines 130, 208, 273, 287, 405 and 419.

At line 144, there''s even:

       if PROTO_AUTH41

(and the preceding line, from the original code:

     if db and @server_capabilities & CLIENT_CONNECT_WITH_DB != 0 then

shows how to express these conditions properly).

So.. it looks as if this patch was never tested with MySQL 4.0. Given 
the elementary nature of the errors, the whole patch needs very careful 
inspection.

regards

   Justin

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Dec 10, 2005, at 1:56 AM, Justin Forder wrote:
> The problem in connecting is not in the AR adapter (I have checked  
> the parameters being passed in to the real_connect call) - it  
> happens within the real_connect method of the mysql.rb driver.
Yes; I did this troubleshooting earlier today.
See http://dev.rubyonrails.org/changeset/3260

> Looking harder at this, it is clear that the problem is not with  
> the driver in its original form (version 0.2.6) from
>   http://www.tmtm.org/en/ruby/mysql/README_en.html
> but with the patch applied to it to make it work with MySQL 4.1.1  
> and above.
The patch is not linked from the english version of the page:
   http://tmtm.org/ruby/mysql/ruby_mysql4.patch
Fixes have been submitted upstream.

> So.. it looks as if this patch was never tested with MySQL 4.0.  
> Given the elementary nature of the errors, the whole patch needs  
> very careful inspection.
Indeed.  Your keen eye is welcome.

Best,
jeremy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (Darwin)

iD8DBQFDmrOUAQHALep9HFYRAp5gAJ44D8+pV52GbvC2TJqAs9J9fHdQ0QCeMdXs
i3RHjgFGy8FSStL2UMdbzpI=V9Ms
-----END PGP SIGNATURE-----

M. Edward (Ed) Borasky wrote:
> David Heinemeier Hansson wrote:
> 
>> It''s been a month since we promised that RC4 would be the
final
>> countdown. And counting down we have. We''ve fixed a ton of
major,
>> minor, and aesthetic issues and now have a package that we would be
>> very proud to call 1.0. No, it''s not completely spotless. A
project of
>> this size with thousands of programmers using it for every application
>> type under the moon will never be. But it''s Pretty Damn Good.
>>  
>>
> [snip]
> 
> "pragdave", et. al. -- is there a corresponding update to
"Agile Web
> Development with Rails" in the works? Those gerbils must be chomping
at
> the bit to build me a copy. :)
> 
It would be good to have wiki pages or Hieraki books covering

- changes in 1.0 relative to the book

- things added since the book was published

   Justin