Yeah, roger the datamodel changes. When I implemented this on my test server, I set the table name to "cr_revisions" rather than "null", which seemed to work, but this required removing the unique constraint on the table name column (can't remember the exact name of the column now). There is actually already an object type in acs_messaging that wants this constraint removed (in 5.1, on oracle), which suggests that it probably shouldn't be there.
Thoughts? And, should I put in a separate TIP to remove or change the constraint?