package DBIx::Class::Serialize::Storable;
use strict;
+use warnings;
use Storable;
sub STORABLE_freeze {
sub STORABLE_thaw {
my ($self,$cloning,$serialized) = @_;
%$self = %{ Storable::thaw($serialized) };
- $self->result_source($self->result_source_instance) if $self->can('result_source_instance');
+ $self->result_source($self->result_source_instance)
+ if $self->can('result_source_instance');
}
1;
__END__
-=head1 NAME
+=head1 NAME
- DBIx::Class::Serialize::Storable - hooks for Storable freeze/thaw (EXPERIMENTAL)
+ DBIx::Class::Serialize::Storable - hooks for Storable freeze/thaw
=head1 SYNOPSIS
__PACKAGE__->load_components(qw/Serialize::Storable/);
# meanwhile, in a nearby piece of code
- my $obj = $schema->resultset('Foo')->find(12);
- $cache->set($obj->ID, $obj); # if the cache uses Storable, this will work automatically
+ my $cd = $schema->resultset('CD')->find(12);
+ # if the cache uses Storable, this will work automatically
+ $cache->set($cd->ID, $cd);
=head1 DESCRIPTION
-This component adds hooks for Storable so that row objects can be serialized. It assumes that
-your row object class (C<result_class>) is the same as your table class, which is the normal
-situation. However, this code is not yet well tested, and so should be considered experimental.
+This component adds hooks for Storable so that row objects can be
+serialized. It assumes that your row object class (C<result_class>) is
+the same as your table class, which is the normal situation.
=head1 AUTHORS