I have an aggregate object with a length method, and I use a length validation on that object with the :allow_nil option set, however when the object is initialized regardless of whether the column its mapped to is nil or not, it breaks this validation. Is this intended behavior? How have others dealt with this? It seems to me the object should be nil if the column is null, much like the one-to-one associations, perhaps it should be configurable to initialize the object with nil parameters. -Jeff _______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails