StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7498581
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2011-09-21T10:58:47.393
FavoriteCount
0
LastActivityDate
2011-09-21T10:58:47.393
LastEditDate
LastEditorUserId
0
OwnerUserId
864651
ParentId
7493472
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Amazingly, after reading a blog post this evening, and some more trial and error, I worked this out myself. You need to assign an <code>@user</code> variable in the 'new' action so that the user params are available for use in the 'create' action. You then need to use both the <code>@account</code> and <code>@user</code> variables in the view. The changes look like this. Accounts Controller: <pre><code>def new @account = Account.new @user = @account.users.build end def create @account = Account.new(params[:account]) @user = @account.users.build(params[:account][:user] if @account.save flash[:success] = "Welcome." redirect_to @account else render :new end end </code></pre> The accounts/new view changes to: <pre><code>= simple_form_for @account do |f| = f.input :name = f.simple_fields_for [@account, @user] do |u| = u.input :email = u.input :password = u.input :password_confirmation = f.button :submit, :value => "Sign up" </code></pre> In this case the params remain nested but have the <code>user</code> component explicitly defined: <pre><code>:account {"name"=>"In", "user"=>{"email"=>"user@example.com", "password"=>"pass", "password_confirmation"=>"pass"}} </code></pre> It has the additional side effect of removing the <code>@account.users.build</code> from within the <code>else</code> path as @numbers1311407 suggested I am not certain whether their are other implications of this solution, I will need to work through it in the next few days, but for now I get the information I want defaulted into the view in the case of a failed <code>create</code> action. @Beerlington and @numbers1311407 I appreciate the help in guiding me to the solution.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPassing params to a new template on a failed create action when using accepts_nested_attributes_for
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USnmott
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. COThis will work, but what you're doing is actually circumventing `accepts_nested_attributes_for` and handling the association build manually. Check my new answer for what the real problem was with your original.
 singulars
 PostPostId
 PO
 UserUserId
 USnumbers1311407

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.