[Glass] Cleaning up TimeZone class history
Dale Henrichs via Glass
glass at lists.gemtalksystems.com
Sun Jul 17 06:09:11 PDT 2016
Paul,
The class histories for base classes is (usually) intentional ... There
are about a half dozen base classes that have class histories and I
don't think it's necessary to clean up their class history ... most of
the class histories are there to support upgrades, but IIRC one or two
of them are there to support useful functionality (i.e., MultiByteString
is in the class history of String so that #isKindOf: 'works') ...
Dale
On 7/16/16 4:49 PM, PAUL DEBRUICKER via Glass wrote:
> Hi -
>
> In my stone I have ObsoleteTimeZone & ObsoleteTimeZone2 in the TimeZone class history of a stone I just updated to 3.3.1. The DataCurator user doesn't have permissions to migrate those classes apparently. And when I sign in as the SystemUser in linked Topaz the Smalltalk symbol is not understood.
>
> To do the migration I'm running:
>
> System abort.
> System beginTransaction.
> [ :className |
> | c |
> c := Smalltalk at: className.
> c isBehavior
> ifTrue: [
> [ c classHistory size > 1 ]
> whileTrue: [
> (c classHistory at: 1) migrateInstancesTo: c classHistory currentVersion.
> c classHistory removeVersion: (c classHistory at: 1) ] ] ]
> value: #'TimeZone'.
> System commitTransaction
>
>
>
> Thanks
>
>
> Paul
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass
More information about the Glass
mailing list