Changes for version 1.29 - 2013-12-18
- Changes to tests only FAILs seen by David Cantrell on 1.28 caused by running of multiple test instances in parallel. All tests were using same database and trampling on each other. Solution is to create unique database for each test run. There may also be cases where tester cannot create new databases. For such cases, tests use preexisting 'test' database. BUT... While developing these changes, the only two CPAN testers that were previously able to run the test suite (Slaven Rezić and David Cantrell) no longer can do so.
- For Cantrell, the issue I think is that the new version of DBD::mysql (4.025) is FAILing its tests, and Cantrell's tester also tries to install the latest version of dependencies.
- For Rezić, I have no clue.
Documentation
Schema information for one collection
Compare two collection definitions and maintain differences
One registration for Class::AutoDB::Registry
Schema information for an AutoDB database
Compare two registries and maintain differences
Serialization engine for Class::AutoDB -- MySQL only for now
Schema information for one table
Modules
Almost automatic object persistence coexisting with human-engineered database
Provides
in lib/Class/AutoDB/BaseTable.pm
in lib/Class/AutoDB/Collection.pm
in lib/Class/AutoDB/CollectionDiff.pm
in lib/Class/AutoDB/Connect.pm
in lib/Class/AutoDB/Cursor.pm
in lib/Class/AutoDB/Database.pm
in lib/Class/AutoDB/Dumper.pm
in lib/Class/AutoDB/Globals.pm
in lib/Class/AutoDB/ListTable.pm
in lib/Class/AutoDB/Object.pm
in lib/Class/AutoDB/Oid.pm
in lib/Class/AutoDB/OidDeleted.pm
in lib/Class/AutoDB/Registration.pm
in lib/Class/AutoDB/Registry.pm
in lib/Class/AutoDB/RegistryDiff.pm
in lib/Class/AutoDB/RegistryVersion.pm
in lib/Class/AutoDB/Serialize.pm
in lib/Class/AutoDB/Table.pm