Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You wil be surprised - it cannot work!</p> <p>Ok the reason can be found in the Rails code. First validation will run the code:</p> <pre><code># Validations module # Returns the Errors object that holds all information about # attribute error messages. def errors @errors ||= Errors.new(self) end </code></pre> <p>As it is a first run then it will create new instance of Errors class. Simple, isn't it? But there is a gotcha - the parameter is self. In your case it is "contact" object.</p> <p>Later then when you call this again on cloned object, the @errors instance will not be created again - as it is not null. And there it is! Instead of passing "cloned" self, the older self is used.</p> <p>Later in the validation code there the Errors class runs the code that read the value from @base which is the <em>self</em> from the initialization. Can you see it? The values for test are read from original model not from the clone! So the validation on "cloned" object runs on values from the original.</p> <p>Ok, so far for the "why not" and now a few words about "how to".</p> <p>The solution is simple - just set @errors to nil after cloning and before validation. As it is quite private, the simple assignment doesn't work. But this works:</p> <pre><code>cloned.instance_eval do @errors = nil end </code></pre> <p>And some tip for interesting reading: <a href="http://yehudakatz.com/2010/01/10/activemodel-make-any-ruby-object-feel-like-activerecord/" rel="nofollow">http://yehudakatz.com/2010/01/10/activemodel-make-any-ruby-object-feel-like-activerecord/</a></p> <p>It is quite comprehensive explanation how the validations in Rails 3 works.</p>
    singulars
    1. This table or related slice is empty.
    1. PORails3: Cloning already-validated object prevents clone being invalidated -- is this strange or normal?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USRadek Paviensky
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PORails3: Cloning already-validated object prevents clone being invalidated -- is this strange or normal?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    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. COThanks, I'm going to have to really think a while about that one but doubtless I'll learn something in the process. I'm too used to simple procedural languages and sometimes the subtleties of objects totally pass me by.
      singulars
      1. PO
      1. USMike Blyth
 

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