Rails - Apr 2005 - Odd ActiveRecord#valid? behavior

I found that some of my records from a pre-existing database will 
occasionaly not be valid. There is no custom validation code on the class, 
but you can do something like:

c = CollectionSession.find 24098
c.valid? 
=> false
c.errors.empty?
=> true

What''s odd is that the code in validations.rb looks like it runs the
various
validations, and then just returns c.errors.empty?

Any ideas? It does use a custom table name, and a custom primary key. It is 
consistant about which records are labeled invalid.

.adam sanderson


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

Well, disregard my post.
Alternatively, you might find it entertaining to know that my class is used 
to track data collected from some very error prone datasources, so it has to 
be checked for validity by a human. I put in a convienence method as 
follows:

def valid?
state > 0
end

Great way to confuse ActiveRecord ;) I think that will become
''state_valid?''
And after all that mucking around in the debugger too!
.adam sanderson


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