doesn't seem to be a good way to determine if a filehandle is readable. And, if the
filehandle isn't readable, it's not clear what will happen. So, don't do that.
+=head2 ASSIGNMENTS WITHIN TRANSACTIONS
+
+The following will I<not> work as one might expect:
+
+ my $x = { a => 1 };
+
+ $db->begin_work;
+ $db->{foo} = $x;
+ $db->rollback;
+
+ is( $x->{a}, 1 ); # This will fail!
+
+The problem is that the moment a reference used as the rvalue to a DBM::Deep
+object's lvalue, it becomes tied itself. This is so that future changes to
+C<$x> can be tracked within the DBM::Deep file and is considered to be a
+feature. By the time the rollback occurs, there is no knowledge that there had
+been an C<$x> or what memory location to assign an C<export()> to.
+
+B<NOTE:> This does not affect importing because imports do a walk over the
+reference to be imported in order to explicitly leave it untied.
+
=head1 CODE COVERAGE
B<Devel::Cover> is used to test the code coverage of the tests. Below is the
+++ /dev/null
-use strict;
-use Test::More tests => 7;
-use Test::Deep;
-use t::common qw( new_fh );
-
-use_ok( 'DBM::Deep' );
-
-my ($fh, $filename) = new_fh();
-my $db = DBM::Deep->new(
- file => $filename,
- locking => 1,
- autoflush => 1,
- num_txns => 16,
-);
-
-my $outer = { a => 'b' };
-my $inner = { a => 'c' };
-
-$db->{x} = $outer;
-is( $db->{x}{a}, 'b', "BEFORE: We're looking at the right value from outer" );
-
-$db->begin_work;
-
- $db->{x} = $inner;
- is( $db->{x}{a}, 'c', "WITHIN: We're looking at the right value from inner" );
-TODO: {
- local $TODO = "Transactions not done yet";
- is( $outer->{a}, 'b', "WITHIN: We're looking at the right value from outer" );
-}
-
-$db->commit;
-
-is( $db->{x}{a}, 'c', "AFTER: Commit means inner is still correct" );
-TODO: {
- local $TODO = "Transactions not done yet";
-is( $outer->{a}, undef, "AFTER: outer made the move" );
-}
-is( $inner->{a}, 'c', "AFTER: inner made the move" );