On Wed, Sep 19, 2012 at 06:37:30AM -0700, Bill Moseley wrote: > On Wed, Sep 19, 2012 at 3:38 AM, Peter Rabbitson <rabbit+d...@rabbit.us>wrote: > > > > > > > Only thing I can think of is to hunt down every place an object is > > > serialized and thawed and just store an ID and then refetch from the > > > database on thaw. Kind of defeats the entire purpose of caching these in > > > the first place. > > > > > > > Did you ever resolve this, or do you still need help? > > > > Not really. We decided the effort needed to make old and new DBIC share > serialized items was just worth the time and instead did something like I > quoted above. Turned out there were only a few serialized items and they > were in the session. So, during our migration (where we will have both old > and new DBIC in the same pool of web servers) we just delete the objects > from the session at the end of every request. We don't think this will be > a significant impact on our database.
Right, the problem here is that the class layout changed between the two versions. I will need to think about fixing that, as it isn't trivial. Glad you found a workaround for the time being. _______________________________________________ List: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbix-class IRC: irc.perl.org#dbix-class SVN: http://dev.catalyst.perl.org/repos/bast/DBIx-Class/ Searchable Archive: http://www.grokbase.com/group/dbix-class@lists.scsys.co.uk
