I was wondering if the various bulk migration utilities between multiple databases correctly do deep copies, maintaining relationships with new primary keys, etc.
I have a production DB that has been regularly renamed on a yearly basis to start fresh. I'd like to merge them into one now, retaining all deep relationships. One approach is to merge them all into the production DB and use present date fields to distinguish between them, but another idea, perhaps foolish, is to dumb them into a different entity type that inherits from a common ancestor, thus separating archived records from current records. Any insight on whether the tools of note are up to the task? _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
