Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change after_save hook to after_commit #3

Merged
merged 1 commit into from Apr 23, 2013

Conversation

barkerja
Copy link
Contributor

I'm not sure if this has any undesirable effects, but I had an issue with the indexer not picking up the right values for columns that are modified/set by (sql) triggers.

Using after_commit ensures that the indexer runs only after the SQL transaction has successfully been committed.

@EvilFaeton
Copy link
Owner

after_commit was added only in 3.0, but i'm not sure about compatibility other dependencies with 2.3.xbranch, so that's ok.

EvilFaeton added a commit that referenced this pull request Apr 23, 2013
Change after_save hook to after_commit
@EvilFaeton EvilFaeton merged commit 1e8dfce into EvilFaeton:master Apr 23, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants