Counter Culture getting incorrect count with after_create hook about counter_culture HOT 3 CLOSED

Hah! That was a fun little distraction. Fixed in 0.1.10. Not sure about the wisdom of triggering an update on the same model instance in an after_create. But, hey, this fix doesn't hurt other use cases, so why not.

In case you are curious: The update_column you did from within after_create fired a separate call to counter_culture's after_update, but all within the same save. That triggered another increment. I'm now checking for that specifically.

from counter_culture.

Awesome, thank you so much and thanks for responding so quickly. You got that done quick!

I'm totally in agreement on the update after save (this particular instance was a strange edge case dealing with a legacy schema).

I thought it might be something like that, I'll check out the changes you made and see how you fixed it so maybe I can help in the future.

Thanks again!

from counter_culture.

Happy to help! This is the commit that fixes this, in case you are curious:
bestvendor/counter_culture@6cd8491

On Wed, Mar 27, 2013 at 4:37 PM, Dan Ahern [email protected] wrote:

Awesome, thank you so much and thanks for responding so quickly. You got
that done quick!

I'm totally in agreement on the update after save (this particular
instance was a strange edge case dealing with a legacy schema).

I thought it might be something like that, I'll check out the changes you
made and see how you fixed it so maybe I can help in the future.

Thanks again!

—
Reply to this email directly or view it on GitHubhttps://github.com/bestvendor/counter_culture/issues/11#issuecomment-15551531
.

from counter_culture.