Migration headache

[Chris Muller]

Hey, what do you think about upgrading MagmaTruncationWarning with an
instVar, 'truncatedObjects' or something of your preference.

Then just update #warnOfTruncationsIn: to populate it.  Then Gjaller
can interrogate the objects and decide whether it wants to pass or
resume the warning.

You are a developer in the MagmaTester project on SqueakSource.  Let
me know if you do it, I'll merge it in.

Regards,
  Chris



On Wed, Mar 4, 2009 at 1:10 AM, Göran Krampe <goran at krampe.se> wrote:
> Hi!
>
> Chris Muller wrote:
>>
>> Hi,
>>
>>> I will take a look at the repo definition, how can I "inspect" the object
>>> buffers in an easy way? It really would be cool to have some kind of low
>>> level explorer that does NOT deserialize/serialize these guys.
>>
>> Ah, MagmaBufferController has been around since 2005 for this exact
>> purpose!   :-)   It's in the "Magma Tools" package in the MagmaTester
>> project of squeaksource.  You may wish to make a simple UI to render
>> the buffers, I made one in Maui in about 37 seconds..  :)
>
> Ah, nice. Will take a look.
>
>>> Yes, but... let's say I have tons of objects in the db with this
>>> superfluous
>>> ivar in them. Every time I pull one of those guys into the image and
>>> changes
>>> it and commits it back - it will warn me. Fine. But how do I fix it "bulk
>>> wise"? I could iterate over them, but how do I tell Magma that:
>>>
>>> "Yes, consider it modified, although it is not, but I want to commit and
>>> truncate all these guys now in order to not get warnings for the rest of
>>> my
>>> life..." :)
>>
>> Heh, ok, there are two separate issues here, the warning and the
>> truncation.  Yes, I had to look up whether a truncation is considered
>> a "change" and it appears it is not.  But this is actually a good
>> thing; or at least the "more conservative" thing.
>
> Yes.
>
>> It sounds like you only care about truncation to the extent it rids
>> the warning.  Can't you just handle and resume that where you perform
>> your commit?  Perhaps you have commits all over the code?  Hmm..  If
>> so, I suppose you could extend MagmaTruncationWarning with:
>>
>>  defaultAction
>>    self resume
>>
>> or some such..?
>
> Well, I ended up doing just that - and no, the commits in Gjallar are not
> spread out. BUT... this means I ignore all truncation warnings from now on!
> Not exactly what I wanted to do... :)
>
> regards, Go"ran
>
> _______________________________________________
> Magma mailing list
> Magma at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/magma
>