Perry Smith wrote:
>
>> So I guess this rules out all but a some plugin interference; I'll look
>> into it;
>>
I finally was able to figure out what was going on.
It was interference from the be9-acl9 gem which is based on acl9 with
some SQL query generation improvements (as of v 0.11)
The par
> So I guess this rules out all but a some plugin interference; I'll look
> into it;
> Do you know of a good way to do this?
What database are you using? Maybe this feature is just for some of the
databases but not all? (That wouldn't make much sense to me but its a
thought.)
It seems like
In fact, I just tried the most simple case and I see an mySQL update
>> a = Language.first
Language Load (0.5ms) SELECT * FROM `languages` LIMIT 1
++-++
| id | name| locale |
++-++
| 1 | Español | es |
++-++
1 row in set
>>
Perry Smith wrote:
> Jose Ambros-ingerson wrote:
>> Frederick Cheung wrote:
>>
>> THanks Fred and Perry for your replies.
>> I followed up on your suggestions yet I have not been able to make it
>> work as advertised.
>> As shown in the example below I've made sure that
>> ActiveRecord::Base.pa
Jose Ambros-ingerson wrote:
> Frederick Cheung wrote:
>> On May 27, 10:55�pm, Jose Ambros-ingerson
>> wrote:
>>
>> Actually that bit in the logs show the name getting set to spanish as
>> well. It's also possible that you've turned off this behaviour -
>> ActiveRecord::Base.partial_updates (or so
Frederick Cheung wrote:
> On May 27, 10:55�pm, Jose Ambros-ingerson
> wrote:
>
> Actually that bit in the logs show the name getting set to spanish as
> well. It's also possible that you've turned off this behaviour -
> ActiveRecord::Base.partial_updates (or something along those lines)
> control
On May 27, 10:55 pm, Jose Ambros-ingerson
wrote:
> Perry Smith wrote:
>
> > By the way, update_attributes calls save (as of 2.3.2? or was it before
> > that) only if at least one attribute has changed.
>
> It appears to me that this is not true. I tried it below using 2.3.5.
> As you can see the
Jose Ambros-ingerson wrote:
> Jose Ambros-ingerson wrote:
>> Perry Smith wrote:
>>
>>>
>>> By the way, update_attributes calls save (as of 2.3.2? or was it before
>>> that) only if at least one attribute has changed.
>>
>
> Though failure to behave this way (see above) is hurting me;
> I have
Jose Ambros-ingerson wrote:
> Perry Smith wrote:
>
>>
>> By the way, update_attributes calls save (as of 2.3.2? or was it before
>> that) only if at least one attribute has changed.
>
Though failure to behave this way (see above) is hurting me;
I have an observer that get's triggered on the sa
Perry Smith wrote:
>
> By the way, update_attributes calls save (as of 2.3.2? or was it before
> that) only if at least one attribute has changed.
It appears to me that this is not true. I tried it below using 2.3.5.
As you can see the 'locale' attribute was "es" and it got updated to
"es" any
Wow, thanks for such great feedback Perry and Fred! You both hit the
point from multiple angles, all of which are important. Thank you
both very much for your help!
On Jun 9, 6:02 pm, Perry Smith
wrote:
> Phoenix Rising wrote:
> > So - and somebody please verify or correct my understanding - a
Phoenix Rising wrote:
> So - and somebody please verify or correct my understanding - as long
> as the hash I pass in to update_attributes doesn't overwrite my prior
> manual assignment methods, this functionality should continue -
> through future updates to the framework - to work as expected -
On Jun 9, 10:51 pm, Phoenix Rising wrote:
>
> # File vendor/rails/activerecord/lib/active_record/base.rb, line
> 2619
> 2619: def update_attributes(attributes)
> 2620: self.attributes = attributes
> 2621: save
> 2622: end
>
> What I don't "get" is how self.attrib
Hey Perry,
Thanks for the reply. As for multiple calls to save, I don't have
that in my example (because I'm not doing it). What I meant was that,
say instead of calling update_attributes, I called save right after
the manual assignment, then called update_attributes again to update
attributes
On Jun 9, 10:05 pm, Perry Smith
wrote:
> I don't see the "multiple" calls to save.
>
> update_attributes will call save but I don't see the other call to save.
>
> By the way, update_attributes calls save (as of 2.3.2? or was it before
> that) only if at least one attribute has changed.
Actual
I don't see the "multiple" calls to save.
update_attributes will call save but I don't see the other call to save.
By the way, update_attributes calls save (as of 2.3.2? or was it before
that) only if at least one attribute has changed.
--
Posted via http://www.ruby-forum.com/.
--~--~
16 matches
Mail list logo
