Dependency walker
Walk large collections in batches of 100 results

Instead of loading all of a large collection into memory at once, load
only batches of 100 results at a time, pushing the remaining collection
back onto the stack each time, to revisit later.
Add the concept of a UID to records
Base-bones Dependencies method, which examines _Accessible for two common fields
Attributes on objects
Transactions, optimized to object types that have them
ObjectCustomFieldValues, optimized to object types that have them
Ensure that RT::Link's ClassAccessible is built early enough
Dependencies
Ensure that we always load merged tickets separately
Bare-bones serializer
Simplest Serialize method possible
Use _ClassAccessible and ->can to deduce possible inflated columns
Serialize ObjectType and ObjectId into a single UID reference
Slightly more comprehensive set of base objects to copy
Output serialized data into bite-sized chunks
Serializing less than the whole db
Serialize some global properties all of the time
Better Serialize methods
Allow us to skip deleted tickets