Now I can proccess 1250 transactions from a csv file in less than 3 SECONDS including the time openning and proccessing of the file.
Great! It's illustrative of the strengths of those two different parts of Magma.
Other thing, after the refactoring I'm getting an error when I change anything on the class structure of any class. The error is: "MaObjectSerializationSoftwareError: Individual not defined in this image". That I did was rename two customer subclasses: Previous: Customer Individual Organization Now: Customer NaturalPerson (Persona Física) LegalPerson (Persona Jurídica) It's strange to me because now all seem works ok and because when I rename that classes haven't persistent instances on magma repository.
Do you now that I'm doing wrong? Is it possible rename a persistent class?
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.
- Chris
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.
- Chris
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.
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.
I would like to but I simply don't have the luxury of time to be able to work on that (unless it would pay something). So, for now I just do what I can here in the Magma mailing list.
But yes, it is my hope that someone will eventually step up and become a expert / co-maintainer of Magma.
- Chris
I would like to but I simply don't have the luxury of time to be able to work on that (unless it would pay something).
Maybe, ESUG can pay for it. They are funding many interesting smalltalk projects. I don't know just I was thinking aloud.
So, for now I just
do what I can here in the Magma mailing list.
Fine for me.
But yes, it is my hope that someone will eventually step up and become a expert / co-maintainer of Magma.
I would like it, I'll need more time too.
- Chris
Facu
magma@lists.squeakfoundation.org