On 21 oct, 17:38, Jeremy Evans <[email protected]> wrote: > On Wed, Oct 21, 2009 at 2:48 AM, Florent <[email protected]> wrote: > > On 20 oct, 20:55, Jeremy Evans <[email protected]> wrote: > >> Ah, obviously my lack of experience with ruby's marshalling has shown > >> through. It makes sense to me now why it fails, but unfortunately I > >> can't think of an easy to to fix it without overriding Model#_dump and > >> Model._load to not attempt to serialize @this (which is not something > >> I want to attempt). I should probably revert at least that part of > >> the commit. > > >> My proposed fix is to add a Model#serializable! method that removes > >> everything that would not be serializable. You'd have to call this > >> first before attempting to serialize a model object safely. Thoughts? > > > it's not a big deal to have to serialize the model before caching it. > > I think that's the good way to do it. > > OK. If that's something you could work on a patch for, I'd appreciate > it. It's on my todo list, but not very high up there. If I have to > work on it, it might make it into 3.6.0, but I could see it slipping > to 3.7.0.
I think I can manage to make a plugin compatible with memcached but to do myself the serializable! method, I don't know if I will know what to remove or not. But I can try, I will probably bother you with some questions about sequel models to do so :) Florent --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sequel-talk" 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/sequel-talk?hl=en -~----------~----~----~----~------~----~------~--~---
