# Rails-0.14.3 Error?

**URL:** <https://www.ruby-forum.com/t/rails-0-14-3-error/47570>\
**Category:** Rails\
**Created:** [November 12, 2005, 12:49pm UTC](https://www.ruby-forum.com/t/rails-0-14-3-error/47570 "2005-11-12T12:49:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![peter.j.donald](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/b5ac83/32.png) [@peter.j.donald](https://www.ruby-forum.com/u/peter.j.donald)\
**Post date:** [November 12, 2005, 12:49pm UTC](https://www.ruby-forum.com/t/rails-0-14-3-error/47570/1 "2005-11-12T12:49:30Z")

</div>

Hi,

I upgraded to 0.14.3 from 0.14.2 and started receiving an error for  
the following code;

class Project \< ActiveRecord::Base  
…  
has\_many :versions, :order =\> ‘position ASC’  
…  
def unarchived\_versions  
versions.select {|v| ! v.archived }  
end  
…

The error is the following

undefined method `sanitize\_sql’ for ActiveRecord::Version:Module

c:/applications/ruby/lib/ruby/gems/1.8/gems/activerecord-1.13.0/lib/active\_record/associations/association\_proxy.rb:64:in  
`send' c:/applications/ruby/lib/ruby/gems/1.8/gems/activerecord-1.13.0/lib/active_record/associations/association_proxy.rb:64:in`sanitize\_sql’  
c:/applications/ruby/lib/ruby/gems/1.8/gems/activerecord-1.13.0/lib/active\_record/associations/has\_many\_association.rb:6:in  
`initialize' c:/applications/ruby/lib/ruby/gems/1.8/gems/activerecord-1.13.0/lib/active_record/associations.rb:735:in`new’  
c:/applications/ruby/lib/ruby/gems/1.8/gems/activerecord-1.13.0/lib/active\_record/associations.rb:735:in  
`issue_versions' c:/applications/ruby/lib/ruby/gems/1.8/gems/activerecord-1.13.0/lib/active_record/associations.rb:731:in`issue\_versions’  
#{RAILS\_ROOT}/app/models/project.rb:13:in `unarchived\_versions’

I am not sure whether it is something I am doing wrong or not. Version  
may be new to 0.14.3 (Added on 10/09/05 21:15:45) so it may be that  
there is some sort of name collision.

My question is whether this is the case and if it is - is there anyway  
to insulate ourselves from changes to the core of rails or do we just  
change everytime a new release comes out. It seems fairly problematic  
if generic names like “Version” stop being able to be used as model  
names.

Cheers,

Peter D.

---

<div class="post-metadata">

**Author:** ![peter.j.donald](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/b5ac83/32.png) [@peter.j.donald](https://www.ruby-forum.com/u/peter.j.donald)\
**Post date:** [November 12, 2005, 12:49pm UTC](https://www.ruby-forum.com/t/rails-0-14-3-error/47570/2 "2005-11-12T12:49:30Z")

</div>

> I upgraded to 0.14.3 from 0.14.2 and started receiving an error for  
> the following code;
> 
> class Project \< ActiveRecord::Base

## Please do post bug reports like this as a ticket on [dev.rubyonrails.org](http://dev.rubyonrails.org). Thanks!

David Heinemeier H.  
[http://www.loudthinking.com](http://www.loudthinking.com) – Broadcasting Brain  
[http://www.basecamphq.com](http://www.basecamphq.com) – Online project management  
[http://www.backpackit.com](http://www.backpackit.com) – Personal information manager  
[http://www.rubyonrails.com](http://www.rubyonrails.com) – Web-application framework