Okey, what the hell. Now it works, as its updating just that changed column. But why save is raising that error?
On Wednesday, September 24, 2014 9:59:22 PM UTC+2, Jeremy Evans wrote: > > On Wednesday, September 24, 2014 12:23:19 PM UTC-7, Petr Kaleta wrote: >> >> Calling save changes returns nil and doing simply nothing. And thats even >> more strange... Going to prepare demo >> >> On Tuesday, September 23, 2014 7:57:38 PM UTC+2, Jeremy Evans wrote: >>> >>> My current guess is the error you are getting is related to a different >>> column than the hstore column. Can you use save_changes instead of save >>> and see if the results are different? >>> >>> If you still get the same error with save_changes, please create a >>> small, self contained example showing the problem, and I'll try to help >>> debug. >>> >> > Ah, that's because you are mutating the value. Try: > > model.modified!(:hstore_attr) > model.save_changes > > Thanks, > Jeremy > -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/d/optout.
