I've got a message queue running, and record ids get added to it in an after_create callback.
However, the message queue is so fast that it can't find the records. This is because the record hasn't actually been saved back to the database yet - after_create is called in the transaction. There's more information on this problem here: http://elimiller.blogspot.com/2007/06/proper-cache-expiry-with-aftercommit.html I'm wondering, is there a reason why after_save and after_create are called inside the transaction? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
