StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14615258
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-01-30T22:39:41.863
FavoriteCount
0
LastActivityDate
2013-02-01T00:27:51.243
LastEditDate
2013-02-01T00:27:51.243
LastEditorUserId
367265
OwnerUserId
367265
ParentId
14614886
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I'd suggest you think about this in behavioural rather than implementation terms. You mention there are three contact forms, but what is the underlying use that you're putting each one to? You shouldn't be thinking about forms when you're setting up your model. That having been said, you can achieve what you want using <a href="https://github.com/gtd/validation_scopes" rel="nofollow">the validation_scopes gem</a>. Using validation_scopes, you can define sets of validation rules that you can treat independently. In your controllers, you can then check whichever set of validation rules apply to the context (i.e. which form the user has filled in). In your model you can set up validation scopes named for each form (or better, named for the context in a way that has semantic value, but I don't know enough about your app to know what the contexts are), like this: <pre><code>validation_scope :form_one_errors do |vs| validates :name, :body, :presence => true end validation_scope :form_two_errors do |vs| validates :aaa, :bbb, :ccc, :presence => true end </code></pre> Since email needs to be validated in both contexts, you can just set it up as a normal validation (as per your code in the question). Then in the controller for, say, form one, you can check the scope to see if there are any errors for that context. Note that you have to check the errors for the validation scope separately for the regular validation errors. <pre><code>if !message.valid? # Do something with message.errors elsif message.has_form_one_errors? # Do something with message.form_one_errors else # All good end </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORails - one model, 2 kinds of validation rules
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USmicapam
UserOwnerUserId
1. USmicapam
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. CODid you check out validation_scopes, user984621? I've added some code examples to my answer to make it clearer how you can use it.
 singulars
 PostPostId
 PO
 UserUserId
 USmicapam

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.