Hi Jairo, If you're memcaching entities the obvious way (memcache.set(key, a_model)), your models are being pickled (using the Python 'pickle' module). When they're restored, pickle looks for the original definition of the class, using the module name that was pickled along with the entity. If you move the definition, it won't be able to find them.
This isn't a memcache bug, but rather an inevitable consequence of how pickling works. For details on an alternate way to memcache models, see my post here: http://blog.notdot.net/2009/9/Efficient-model-memcaching -Nick Johnson On Wed, Feb 24, 2010 at 8:59 PM, Jairo Vasquez Moreno < [email protected]> wrote: > Hi all, > > I moved my models to another folder and then when I uploaded those changes, > there was a memcache error saying that model was not found. I had to do > flush_all and everything started to work. Is that a memcache bug? Is > memcache using the path of the model for data saved in memcache? > > -- > Jairo Vasquez Moreno > Mentez Developer > www.mentez.com > Medellin - Colombia > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-appengine%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- Nick Johnson, Developer Programs Engineer, App Engine Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number: 368047 -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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/google-appengine?hl=en.
