<div><br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Yes, but you must do it under a transaction. Begin, rename, commit.<br>
If you didn't do it that way, then the repository will think it is<br>
just a new class and you will have to "upgrade" your old instances<br>
with a script.<br>
<br>
See MagmaTestCase>>testClassSchemaUpgrades. It includes a rename test.<br></blockquote><div><br></div><div>Yes, I understand you. Thanks.</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
<br>
> The only person who can help you with this is Chris. Because my<br>
> knowledge about Magma in this area<br>
> are close to zero :)<br>
<br>
The other thing that can help everyone is the *code*. Answers to many<br>
questions are easily found there. It is straightforward, especially<br>
if you pay attention to the package each method is in; because that<br>
reveals what "layer" it operates on.</blockquote><div><br></div><div>Yes, that's true but do you think about a Magma manual or reference? Maybe any of us (users of Magma) can help you if you like, of course. </div>
</div><br>