I''m getting this failing test when running the ActiveRecord mysql
tests on MySQL 5.0.51b (on latest master branch).
1) Failure:
test_nil_defaults_for_not_null_columns(DefaultTest)
[./test/cases/defaults_test.rb:17:in
`test_nil_defaults_for_not_null_columns''
./test/cases/defaults_test.rb:14:in `each''
./test/cases/defaults_test.rb:14:in
`test_nil_defaults_for_not_null_columns''
./test/cases/../../lib/../../activesupport/lib/active_support/
testing/setup_and_teardown.rb:67:in `__send__''
./test/cases/../../lib/../../activesupport/lib/active_support/
testing/setup_and_teardown.rb:67:in `run'']:
name column should be DEFAULT "".
<""> expected but was
<nil>.
It appears MySQL has changed how its defaults work, but before I try
to make a patch, can anyone confirm this problem on their system? Or
is it something wrong with my setup?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Core" group.
To post to this group, send email to rubyonrails-core@googlegroups.com
To unsubscribe from this group, send email to
rubyonrails-core-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en
-~----------~----~----~----~------~----~------~--~---
Yup. Rick faced it a while back http://rails.lighthouseapp.com/projects/8994/tickets/192-ar-test-failure-on-latest-mysql On Wed, May 21, 2008 at 4:53 PM, Ryan Bates <bates.ryan@gmail.com> wrote:> > I''m getting this failing test when running the ActiveRecord mysql > tests on MySQL 5.0.51b (on latest master branch). > > 1) Failure: > test_nil_defaults_for_not_null_columns(DefaultTest) > [./test/cases/defaults_test.rb:17:in > `test_nil_defaults_for_not_null_columns'' > ./test/cases/defaults_test.rb:14:in `each'' > ./test/cases/defaults_test.rb:14:in > `test_nil_defaults_for_not_null_columns'' > ./test/cases/../../lib/../../activesupport/lib/active_support/ > testing/setup_and_teardown.rb:67:in `__send__'' > ./test/cases/../../lib/../../activesupport/lib/active_support/ > testing/setup_and_teardown.rb:67:in `run'']: > name column should be DEFAULT "". > <""> expected but was > <nil>. > > It appears MySQL has changed how its defaults work, but before I try > to make a patch, can anyone confirm this problem on their system? Or > is it something wrong with my setup? > > > >-- Cheers! - Pratik http://m.onkey.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
On May 21, 9:08 am, Pratik <pratikn...@gmail.com> wrote:> Yup. Rick faced it a while backhttp://rails.lighthouseapp.com/projects/8994/tickets/192Glad to see I''m not the only one. Has anyone come up with a good solution to this problem? I guess we have to determine the MySQL version at run time and add a conditional statement in there. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
I added a patch to the ticket which fixes the problem for me. If someone could please test it and make sure it works for them that would be great. http://rails.lighthouseapp.com/projects/8994/tickets/192#ticket-192-2 On May 21, 9:36 am, Ryan Bates <bates.r...@gmail.com> wrote:> On May 21, 9:08 am, Pratik <pratikn...@gmail.com> wrote: > > > Yup. Rick faced it a while backhttp://rails.lighthouseapp.com/projects/8994/tickets/192 > > Glad to see I''m not the only one. Has anyone come up with a good > solution to this problem? I guess we have to determine the MySQL > version at run time and add a conditional statement in there.--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
On 21 May 2008, at 17:55, Ryan Bates wrote:> > I added a patch to the ticket which fixes the problem for me. If > someone could please test it and make sure it works for them that > would be great. >Those tests fail on 4.1 (in a different way. sigh) before & after your patch. I''ll have a look at what mysql have changed Fred> http://rails.lighthouseapp.com/projects/8994/tickets/192#ticket-192-2 > > On May 21, 9:36 am, Ryan Bates <bates.r...@gmail.com> wrote: >> On May 21, 9:08 am, Pratik <pratikn...@gmail.com> wrote: >> >>> Yup. Rick faced it a while backhttp://rails.lighthouseapp.com/projects/8994/tickets/192 >> >> Glad to see I''m not the only one. Has anyone come up with a good >> solution to this problem? I guess we have to determine the MySQL >> version at run time and add a conditional statement in there. > >--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
This reminds me to ask, is there still a CI system running (CruiseControl.rb or something) active for the current Rails repository? And where is it mailing? rgrds, Jan On 22 May 2008, at 11:56, Frederick Cheung wrote:> > > On 21 May 2008, at 17:55, Ryan Bates wrote: > >> >> I added a patch to the ticket which fixes the problem for me. If >> someone could please test it and make sure it works for them that >> would be great. >> > Those tests fail on 4.1 (in a different way. sigh) before & after your > patch. I''ll have a look at what mysql have changed > > Fred >> http://rails.lighthouseapp.com/projects/8994/tickets/192#ticket-192-2 >> >> On May 21, 9:36 am, Ryan Bates <bates.r...@gmail.com> wrote: >>> On May 21, 9:08 am, Pratik <pratikn...@gmail.com> wrote: >>> >>>> Yup. Rick faced it a while backhttp://rails.lighthouseapp.com/projects/8994/tickets/192 >>> >>> Glad to see I''m not the only one. Has anyone come up with a good >>> solution to this problem? I guess we have to determine the MySQL >>> version at run time and add a conditional statement in there. >>> > > > >--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
Don''t think it''s running anymore. On Thu, May 22, 2008 at 11:08 AM, Jan De Poorter <jan@openminds.be> wrote:> > This reminds me to ask, > > is there still a CI system running (CruiseControl.rb or something) > active for the current Rails repository? And where is it mailing? > > rgrds, > Jan > > On 22 May 2008, at 11:56, Frederick Cheung wrote: > >> >> >> On 21 May 2008, at 17:55, Ryan Bates wrote: >> >>> >>> I added a patch to the ticket which fixes the problem for me. If >>> someone could please test it and make sure it works for them that >>> would be great. >>> >> Those tests fail on 4.1 (in a different way. sigh) before & after your >> patch. I''ll have a look at what mysql have changed >> >> Fred >>> http://rails.lighthouseapp.com/projects/8994/tickets/192#ticket-192-2 >>> >>> On May 21, 9:36 am, Ryan Bates <bates.r...@gmail.com> wrote: >>>> On May 21, 9:08 am, Pratik <pratikn...@gmail.com> wrote: >>>> >>>>> Yup. Rick faced it a while backhttp://rails.lighthouseapp.com/projects/8994/tickets/192 >>>> >>>> Glad to see I''m not the only one. Has anyone come up with a good >>>> solution to this problem? I guess we have to determine the MySQL >>>> version at run time and add a conditional statement in there. >>>> >> >> >> > > > > > >-- Cheers! - Pratik http://m.onkey.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
On Thu, May 22, 2008 at 3:08 AM, Jan De Poorter <jan@openminds.be> wrote:> > This reminds me to ask, > > is there still a CI system running (CruiseControl.rb or something) > active for the current Rails repository? And where is it mailing? > > rgrds, > JanI''m gonna work with Alexey to get this going again soon. Sometime next month, after RailsConf (which is currently taking all my free time to prepare for)... Git support is now in ccrb trunk, so theoretically nothing holding is us back. Other than somebody doing it ;) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---