On 19/11/2010, at 11:11 AM, Chris Mayan wrote: > Something akin to a subscriber/publisher design pattern, where I can > subscribe to the DB from rails and say, "Notify me when anything to do with > this row" has changed.. and then when something does change the DB is the one > that communicates back through the db connection signalling to call .reload… > Like I don't understand why this is not a standard in any ORM implementation… > surely it's never a good situation to be dealing with stale objects at any > time
Don't take this the wrong way, but you seem to be misunderstanding the lifecycle of a rails request, and the models it loads during a request? -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to rails-ocea...@googlegroups.com. To unsubscribe from this group, send email to rails-oceania+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
