Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the DateTime-Locale CPAN distribution.

Report information
The Basics
Id: 23655
Status: resolved
Priority: 0/
Queue: DateTime-Locale
People
Owner: Nobody in particular
Requestors: martin.groenemeyer [...] kochpiraten.de
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Mon Nov 27 06:25:35 2006 martin.groenemeyer [...] kochpiraten.de - Ticket created
Subject: Problem with backwards compatibility
Date: Mon, 27 Nov 2006 11:59:38 +0100
To: bug-DateTime-Locale [...] rt.cpan.org
From: martin groenemeyer <martin.groenemeyer [...] kochpiraten.de>
Hello, after a debian update and the installation of DataTime::Locale::VERSION 3.101 I run into trouble. In a web application we store some session data in our database, including a DataTime object. The session data is freezed into a storable. If we thaw a DataTime::Locale::VERSION 2.2 with VERSION 3.101 installed I get this error: "No STORABLE_thaw defined for objects of class DateTime::Locale::en_US". After a look into "diff -r DateTime-Locale-0.3101 DateTime-Locale-0.22 | less" I decided to ask here if there is a simple workaround. In the file CHANGES it says: * BACKWARDS INCOMPATIBILITY. Thanks for this module and best regards, Martin
  Sat Dec 16 14:06:28 2006 DROLSKY [...] cpan.org - Correspondence added
On Mon Nov 27 06:25:35 2006, martin.groenemeyer@kochpiraten.de wrote: Show quoted text
> Hello, > > after a debian update and the installation of DataTime::Locale::VERSION > 3.101 I run into trouble. > In a web application we store some session data in our database, > including a DataTime object. The session data is freezed into a > storable. If we thaw a DataTime::Locale::VERSION 2.2 with VERSION 3.101 > installed I get this error: "No STORABLE_thaw defined for objects of > class DateTime::Locale::en_US". > After a look into "diff -r DateTime-Locale-0.3101 DateTime-Locale-0.22 | > less" I decided to ask here if there is a simple workaround. In the file > CHANGES it says: * BACKWARDS INCOMPATIBILITY.
I don't really have a workaround for this. Generally speaking, the whole freeze/thaw interface is not something you can expect to remain stable across upgrades (for any module), unless the author explicitly tries to do so. In this particular case, however, the problem is that the class in question no longer exists in the new version of the distro. Thawing older objects should actually work if the class exists. I don't really have a good workaround for this. You could define a bunch of empty classes with the needed names that inherit from DT::Locale::Base. Anyway, I'm closing this bug because I don't really think it's a bug, per se.
  Sat Dec 16 14:06:29 2006 The RT System itself - Status changed from 'new' to 'open'
  Sat Dec 16 14:06:30 2006 DROLSKY [...] cpan.org - Status changed from 'open' to 'resolved'