If you're a Rails developer and you're talking about "Data Migration," I'd guess your talking about database management with ActiveRecord? So, ActiveRecord (in the context of Ruby) in an implementation of a design pattern of the same name. ActiveRecord is an ORM, so maybe you should have a look at Glorp (which is also an ORM, but for Smalltalk.)
Also, you should give Magma a try too. I played around with it over a weekend, and was nearly convinced that I'd rather never deal with SQL or ORMs every again. Nearly:) Anyway, most of the time you won't need a database until your app needs to scale past a demo, because you can just use image based persistence when developing.
Hopefully some of that helps.
On Thu, Dec 31, 2009 at 12:29 AM, Friedrich Dominicus frido@q-software-solutions.de wrote:
Dear Smalltalker, I'm trying to get into Smalltalk a bit more seriously. I'm especially currently trying to get into Seaside programmming and the persistence of Objects. I found GLASS, which seems to be remarkabel in that aspect. Now I wonder
- How does one do versioning in Smalltalk. AFAIU it seems, one files
out ChangeSets which then can be read in in another image. Am I wrong about that?
- How does one Data Migration in Smalltalk? I just know it from Rails,
where one has migrations, but how's that done in the Persistence layers of some Smalltalk. E.g what happens if I add or remove instance variables?
There are somewhat related question but more about GLASS. I read teh gemstone soup up and down, and was able to install the Web Edition on my System also. It was a few days work but I learned a lot. However I found just a few videos about Gemstone, but not more "serious" use (with more database related stuff, scheme changes etc) Would you mind to share your experiences?
Regards Friedrich
-- Q-Software Solutions GmbH; Sitz: Bruchsal; Registergericht: Mannheim Registriernummer: HRB232138; Geschaeftsfuehrer: Friedrich Dominicus