# Ruby 1.8.6

**URL:** <https://www.ruby-forum.com/t/ruby-1-8-6/88619>\
**Category:** Rails\
**Created:** [March 13, 2007, 4:45am UTC](https://www.ruby-forum.com/t/ruby-1-8-6/88619 "2007-03-13T04:45:07Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![dysinger](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/958977/32.png) [@dysinger](https://www.ruby-forum.com/u/dysinger)\
**Post date:** [March 13, 2007, 4:45am UTC](https://www.ruby-forum.com/t/ruby-1-8-6/88619/1 "2007-03-13T04:45:07Z")

</div>

I upgraded for fun today and ruby is complaining that rails methods  
are now ‘private’ like ActiveRecord update and Time to\_date

?

---

<div class="post-metadata">

**Author:** ![dysinger](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/958977/32.png) [@dysinger](https://www.ruby-forum.com/u/dysinger)\
**Post date:** [March 13, 2007, 4:51am UTC](https://www.ruby-forum.com/t/ruby-1-8-6/88619/2 "2007-03-13T04:51:08Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![dysinger](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/958977/32.png) [@dysinger](https://www.ruby-forum.com/u/dysinger)\
**Post date:** [March 13, 2007, 5:13am UTC](https://www.ruby-forum.com/t/ruby-1-8-6/88619/3 "2007-03-13T05:13:09Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![dysinger](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/958977/32.png) [@dysinger](https://www.ruby-forum.com/u/dysinger)\
**Post date:** [March 13, 2007, 5:17am UTC](https://www.ruby-forum.com/t/ruby-1-8-6/88619/4 "2007-03-13T05:17:09Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![dysinger](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/958977/32.png) [@dysinger](https://www.ruby-forum.com/u/dysinger)\
**Post date:** [March 13, 2007, 7:07am UTC](https://www.ruby-forum.com/t/ruby-1-8-6/88619/5 "2007-03-13T07:07:17Z")

</div>

On 3/12/07, dysinger [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) 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

---

<div class="post-metadata">

**Author:** ![dysinger](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/958977/32.png) [@dysinger](https://www.ruby-forum.com/u/dysinger)\
**Post date:** [March 13, 2007, 9:12pm UTC](https://www.ruby-forum.com/t/ruby-1-8-6/88619/6 "2007-03-13T21:12:42Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![dysinger](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/958977/32.png) [@dysinger](https://www.ruby-forum.com/u/dysinger)\
**Post date:** [March 13, 2007, 9:51pm UTC](https://www.ruby-forum.com/t/ruby-1-8-6/88619/7 "2007-03-13T21:51:48Z")

</div>

On 3/13/07, dysinger [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) 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 save

Base#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](http://dev.rubyonrails.org/changeset/6396#file5)  
So this is unrelated to Ruby 1.8.6.

jeremy