I upgraded for fun today and ruby is complaining that rails methods are now ''private'' like ActiveRecord update and Time to_date ? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
I get messages like this: NoMethodError: private method `update'' called for #<Xyz:0x33ee2b8> NoMethodError: private method `create'' called for #<Xyz:0x34050f8> Which is a regular ActiveRecord object I''m not seeing the Time to_date NoMethodError that I saw earlier though On Mar 12, 5:44 pm, "dysinger" <dysin...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> I upgraded for fun today and ruby is complaining that rails methods > are now ''private'' like ActiveRecord update and Time to_date > > ?--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Now I am seeing the to_date problem again (strange) NoMethodError: private method `to_date'' called for Tue Mar 13 04:10:37 UTC 2007:Time which is a regular rails extension to Time On Mar 12, 5:49 pm, "dysinger" <dysin...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> I get messages like this: > > NoMethodError: private method `update'' called for #<Xyz:0x33ee2b8> > NoMethodError: private method `create'' called for #<Xyz:0x34050f8> > > Which is a regular ActiveRecord object > > I''m not seeing the Time to_date NoMethodError that I saw earlier > though > > On Mar 12, 5:44 pm, "dysinger" <dysin...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > I upgraded for fun today and ruby is complaining that rails methods > > are now ''private'' like ActiveRecord update and Time to_date > > > ?--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Ahh! The to_date method problem is on rails 1.2.2 The update and create method problem is on rails edge Both of them don''t appear to like Ruby 1.8.6 On Mar 12, 6:12 pm, "dysinger" <dysin...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Now I am seeing the to_date problem again (strange) > > NoMethodError: private method `to_date'' called for Tue Mar 13 04:10:37 > UTC 2007:Time > > which is a regular rails extension to Time > > On Mar 12, 5:49 pm, "dysinger" <dysin...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > I get messages like this: > > > NoMethodError: private method `update'' called for #<Xyz:0x33ee2b8> > > NoMethodError: private method `create'' called for #<Xyz:0x34050f8> > > > Which is a regular ActiveRecord object > > > I''m not seeing the Time to_date NoMethodError that I saw earlier > > though > > > On Mar 12, 5:44 pm, "dysinger" <dysin...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > I upgraded for fun today and ruby is complaining that rails methods > > > are now ''private'' like ActiveRecord update and Time to_date > > > > ?--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
On 3/12/07, dysinger <dysinger-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Ahh! > > The to_date method problem is on rails 1.2.2 > The update and create method problem is on rails edge > > Both of them don''t appear to like Ruby 1.8.6This and other 1.8.6 incompatibilities are fixed in the upcoming Rails 1.2.3 release. Look for it shortly. I haven''t seen that #update/create error on trunk. jeremy --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Ok I got everything working now with rails edge and ruby 1.8.6 Only changes I had to make were no calling create and update on active record models but instead calling save On Mar 12, 8:06 pm, "Jeremy Kemper" <jer...-w7CzD/W5Ocjk1uMJSBkQmQ@public.gmane.org> wrote:> On 3/12/07, dysinger <dysin...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > Ahh! > > > The to_date method problem is on rails 1.2.2 > > The update and create method problem is on rails edge > > > Both of them don''t appear to like Ruby 1.8.6 > > This and other 1.8.6 incompatibilities are fixed in the upcoming Rails > 1.2.3 release. Look for it shortly. > > I haven''t seen that #update/create error on trunk. > > jeremy--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
On 3/13/07, dysinger <dysinger-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Ok I got everything working now with rails edge and ruby 1.8.6 > > Only changes I had to make were no calling create and update on active > record models but instead calling saveBase#create and #update have always been private methods. They ''broke'' because they were accidentally made public by wrapper methods and a recent change made them private again: http://dev.rubyonrails.org/changeset/6396#file5 So this is unrelated to Ruby 1.8.6. jeremy --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---