Changes for version 1.29_02 - 2013-11-02
- Fixed FAIL logic in autodb.000.reqs.t introduced in 1.29_01
Changes for version 1.29_01 - 2013-11-01
- Working on FAILs seen by David Cantrell. Current theory: he runs multiple test instances in parallel, ans since tests all use same database, they are trampling on each other. Solution is to create unique database for each test run.
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