If I understand you correctly, there is one table with two distinct types. You could split this into two tables or use Single Table Inheritance. If you use STI, you would put a type field in the table and then have 3 models:
<br><br>BaseClass<br>PersonA < BaseClass<br>PersonB < BaseClass<br><br>Then the PersonA model and PersonB model would have their own validation, with the common validations in the BaseClass. <br><br>Hope this helps,
<br><br>Ben<br><br><div><span class="gmail_quote">On 3/31/06, <b class="gmail_sendername">Bob Boyken</b> <<a href="mailto:bob@boyken.org">bob@boyken.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I have a single table that two people enter data into. Person A creates<br>the record and I need to specify certain required fields in his form.<br>Person B has a separate form and she fills in additional fields and I<br>
need to specify that some of these are required.<br><br>Since the data is all in one table and since the validations are in the<br>model, won't Rails complain when person A tries to save? I was getting<br>ready to see what would happen, but I thought I'd ask first. Thanks for
<br>the help!<br><br>Bob<br><br>--<br>Posted via <a href="http://www.ruby-forum.com/">http://www.ruby-forum.com/</a>.<br>_______________________________________________<br>Rails mailing list<br><a href="mailto:Rails@lists.rubyonrails.org">
Rails@lists.rubyonrails.org</a><br><a href="http://lists.rubyonrails.org/mailman/listinfo/rails">http://lists.rubyonrails.org/mailman/listinfo/rails</a><br></blockquote></div><br><br clear="all"><br>-- <br>Ben Reubenstein
<br><a href="http://www.benr75.com">http://www.benr75.com</a>