Magma tester-cmm.184

[Chris Muller]

> Could you clarify the expected behaviour for me w.r.t the renamed indexes.
> 
> I have a huge Magma repository generated using older versions of Magma.
> These contain many index instances, ending with 'Definition'.

Hi Brent, I did not mean to be inconsiderate of your "legacy" (I wish :) )
repositories; I apologize.  I happily renamed those classes with the notion of
complete file-format flexibility in mind.  Btw, has this changed for you?

So here we have an opportunity to see how well it can cope with this.  Magma
sees the indexes as just another "domain" class, and Magma was designed to
allow domain classes to evolve, including renamed.

Try following these steps:

  1) back up your legacy repository, just in case
  2) in an image with the old code, Magma tester-cmm.162 loaded, connect a
session.
  3) Begin a transaction, "self begin".
  4) Open up MaIndexDefinition in a browser.
  5) Using the browser menu, rename MaIndexDefinition to MagmaCollectionIndex. 
Rename the appropriate subclasses to cut off the word "Definition".
  6) commit the transaction.
  7) disconnectAndClose

You should now be able to load the new code, Magma tester-cmm.184, and use your
repository normally.

This is an area of Magma that, while there is one test case for it, well.. 
It's just one test case.  :)

Please let me know how it goes, and don't panic if this doesn't work, we can
certainly debug it or apply a more drastic approach if necessary..

Regards,
  Chris