Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>First off, the params that you pasted include values for the profile's city, country and gender. If this is accurate, then validation <em>should</em> pass, because the <code>Profile</code> model validates the presence of these 3 fields -- and they are present.</p> <p>I also note that you're doing <code>resource.build_profile</code> in the view, which should build up a default profile belonging to the user. If any values are being assigned in the profile during instantiation, this would cause them to make their way into the form, and ultimately into the params hash.</p> <p>So my guess is that you're populating the fields somewhere along the line, perhaps in the <code>User</code> or <code>Profile</code> models. You should check those again, particularly during initialization of a new profile.</p> <p>That's all I can guess at from the data you've given. If you still can't find the issue, you could try committing it (or a separate app which reproduces the issue, if you're uncomfortable sharing your real app) to GitHub so that we can analyze the issue more directly.</p> <p>EDIT: just noticed, in your bounty you wrote:</p> <blockquote> <p>anyone can provide a working example [of] nested resources and validations</p> </blockquote> <p>So, see <a href="https://github.com/sinisterchipmunk/rubytastic" rel="nofollow">https://github.com/sinisterchipmunk/rubytastic</a> for a simple example of user validation with nested attributes for a Profile, modeled after your question. It validates <code>User#email</code>, <code>Profile#city</code>, <code>Profile#country</code> and <code>Profile#gender</code>.</p>
    singulars
    1. This table or related slice is empty.
    1. POserious stuck on: validations not triggered for nested resource with fields_for
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USsinisterchipmunk
    1. USsinisterchipmunk
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIf I leave the 3 fields empty, the form still validates, there are no errors ( I set the 3 profile fields to be required ). Thx a lot for the comment and taking some time to write an example. I check them out tomorrow in full detail and report back then. thx again.
      singulars
      1. PO
      1. USRubytastic
    2. COI used the loop all errors code from your example , didn't think a second about trying that it seems that error styling is not applied. So the fields are invalid but there is no CSS also the forms are not repopulated. Im going to strip my profile model now to see if any code is causing these issues.
      singulars
      1. PO
      1. USRubytastic
    3. COYes, Rails 2 had a `<%= f.error_messages %>` method but it was removed in Rails 3 because the core team felt it was too "magic", in that no one ever really understood what it did. So now you have to do styling yourself, but it's not much more work anyway. The forms might not be repopulated because of your `resource.build_profile`, which might be overwriting the previous (invalid) profile with a brand-new (blank) one.
      singulars
      1. PO
      1. USsinisterchipmunk
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload