Transactions in DBM::Deep are done using a variant of the MVCC method, the
same method used by the InnoDB MySQL engine.
-=head2 Software-Transactional Memory
-
-The addition of transactions to this module provides the basis for STM within
-Perl 5. Contention is resolved using a default last-write-wins. Currently,
-this default cannot be changed, but it will be addressed in a future version.
-
=head1 PERFORMANCE
Because DBM::Deep is a conncurrent datastore, every change is flushed to disk
=back
+=head1 MIGRATION
+
+As of 1.0000, the file format has changed. Furthermore, DBM::Deep is now
+designed to potentially change file format between point-releases, if needed to
+support a requested feature. To aid in this, a migration script is provided
+within the CPAN distribution called C<utils/upgrade_db.pl>.
+
+B<NOTE:> This script is not installed onto your system because it carries a copy
+of every version prior to the current version.
+
=head1 TODO
The following are items that are planned to be added in future releases. These
=item B<-version>
Optionally, you can specify the version of L<DBM::Deep> for the output file.
-This can either be an upgrade or a downgrade.
+This can either be an upgrade or a downgrade. The minimum version supported is
+0.91.
-If the version is the same, this is just like a call to compress().
+If the version is the same as the input file, this acts like a compressed copy
+of the database.
=item B<-autobless>
=item B<-man>
-Prints this longer message, then exits;
+Prints a much longer message, then exits;
=back