StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7297169
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2011-09-04T03:02:16.510
FavoriteCount
0
LastActivityDate
2011-09-04T03:02:16.510
LastEditDate
LastEditorUserId
0
OwnerUserId
729120
ParentId
7296819
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I'm a noob, but i think i can help - not for the view part, but for the logic beneath. It seems you will need an action in your PersonPagesController that will be called on form submission (admitting that your form sends a person_name and a project_name), that should look like : <pre><code>def add_person_to_project @person = Person.find(params[:person_name]) @project = Project.find_or_create_by_name(params[:project_name]) @project.persons << @person # or @person.projects << @project end </code></pre> information on find_or_create can be found there <a href="http://api.rubyonrails.org/classes/ActiveRecord/Base.html" rel="nofollow">http://api.rubyonrails.org/classes/ActiveRecord/Base.html</a> (under "Dynamic Attribute-based Finders") you will obviously have to send the person's name with the form for this to work, which you should be able to do by adding a pre-filled hidden field when generating the empty form for a specific person (i don't know formstatic and nested_form though...). You may also want to secure this a bit ( check if a person is really found, and if that person does not already belong to the project before adding it...) Also, i would generally not advise to use the name fields as keys for your persons and projects, but that's up to you. I would advise, though, that you implement this another way, letting the user choose the project in a list or create a new one (what happens if your user makes a typo for example ?)
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POUsing Has_and_belongs_to_many association in multi model view rails
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USm_x
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POUsing Has_and_belongs_to_many association in multi model view rails
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. COYou did not fully answer my question about the form and view but your example taught me about virtual/hidden fields which i learned more about through railscast (167). So now I have a different (more elegant) way of structuring my view. So now i think i can answer my problem. Thanks a lot
 singulars
 PostPostId
 PO
 UserUserId
 USGTDev

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.