Issue 285 in glassdb: Changing class category does not reset class cache

Status: Accepted
Owner: [hidden email]
Labels: Type-Defect Priority-Medium GLASS-Server Version-1.0-beta.8.7

New issue 285 by [hidden email]: Changing class category does not reset  
class cache
http://code.google.com/p/glassdb/issues/detail?id=285

In GemStone3.0, I have found that just changing the category doesn't reset  
the cached ClassOrganizer (new class version not added which is good, but  
the cache isn't reset which is bad) ... as a result, the class isn't  
visible if you use #listAtCategory: in ClassOrganizer.

Need to look at 2.4 (1.0-beta.8.7) since i've got some optimizations  
scheduled that may suffer from the same bug...

Updates:
        Labels: Milestone-1.0-beta.8.7

Comment #1 on issue 285 by [hidden email]: Changing class category does  
not reset class cache
http://code.google.com/p/glassdb/issues/detail?id=285

(No comment was entered for this change.)

Updates:
        Status: Fixed
        Labels: Fixed-1.0-beta.8.7

Comment #2 on issue 285 by [hidden email]: Changing class category  
does not reset class cache
http://code.google.com/p/glassdb/issues/detail?id=285

fixed in GsMonticello 0.241 (dkh.130).

turns out that just sending #category: to a class triggered this bug so  
fixed that also. Added a couple of tests one for #category: and one for  
Monticello