On 2008/01/01, at 04:57, Christopher Laco wrote:
I've heard mention of this before, but I can't find the thread.
I have the latest DateTime, Storable and
Catalyst::Plugin::Session/Authentication and I've getting heap of
these
in my logs:
Use of uninitialized value in subroutine entry at blib/lib/
Storable.pm (autosplit into blib/lib/auto/Storable/_freeze.al)
line 339.
This seems to be caused by storaing a DateTime object in the
session. If
I store a string instead of a DT instance, the warnings go away.
Anyone have any ideas on this one?
The only thing I can tell you about this is: STAY WAY FROM
SERIALIZING DATETIME INTO STORABLE!
I've had a project that did that, and I had tons of problems, some
like the warnings you mentioned and others resulting in real 'dies'.
I've asked this mailling list without any good tip. I was so angry
then that I solved my problem once and for all by storing the
individual parts of datetime in the storable (month, day, year, ....).
Probably the stupidest solution, but it solved my problems after 1
month of battle.
Ruben
-=Chris
_______________________________________________
List: [email protected]
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/
[email protected]/
Dev site: http://dev.catalyst.perl.org/
---------------------------------------------------------
Rúben Fonseca <[EMAIL PROTECTED]>
Technical Consultant
log <www.log.pt>
Tel: +351 21 330 42 20
Fax: +351 21 330 42 19
Calçada Marquês de Abrantes, 45 - 3º Dto
1200-718 Lisboa
---------------------------------------------------------
_______________________________________________
List: [email protected]
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
