Renaming persistent classes

Facundo Vozzi facundov79 at gmail.com
Mon Dec 13 12:23:56 UTC 2010


>
> Yes, but you must do it under a transaction.  Begin, rename, commit.
> If you didn't do it that way, then the repository will think it is
> just a new class and you will have to "upgrade" your old instances
> with a script.
>
> See MagmaTestCase>>testClassSchemaUpgrades.  It includes a rename test.
>

Yes, I understand you. Thanks.

>
>
> > The only person who can help you with this is Chris. Because my
> > knowledge about Magma in this area
> > are close to zero :)
>
> The other thing that can help everyone is the *code*.  Answers to many
> questions are easily found there.  It is straightforward, especially
> if you pay attention to the package each method is in; because that
> reveals what "layer" it operates on.


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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/magma/attachments/20101213/9f047bea/attachment.htm


More information about the Magma mailing list