Re: Issue 132 in glassdb: Use System class>>#'_cacheName:' to make session recognizable in vsd

Updates:
        Labels: -Milestone-3.0 Milestone-1.0-beta.8.7

Comment #4 on issue 132 by [hidden email]: Use System  
class>>#'_cacheName:' to make session recognizable in vsd
http://code.google.com/p/glassdb/issues/detail?id=132

(No comment was entered for this change.)

Comment #5 on issue 132 by [hidden email]: Use System  
class>>#'_cacheName:' to make session recognizable in vsd
http://code.google.com/p/glassdb/issues/detail?id=132

Since I'm the one who reported this I'll note that my initial suggestion  
isn't quite right. VSD expects that the name must be unique, so the name  
should be something like the following:
     ((x := 'GemTools-' , (GsSession serialOfSession: System session)  
printString , '-' , System myUserProfile userId) copyFrom: 1 to: (x size  
min: 31)).

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

Comment #6 on issue 132 by [hidden email]: Use System  
class>>#'_cacheName:' to make session recognizable in vsd
http://code.google.com/p/glassdb/issues/detail?id=132

fixed in GemTools 1.0-beta.8.5 (dkh.137), GemStone 2.4.5 and GemStone 3.0.1.

Maintenance VM, Seaside gems and GemTools gem have unique cacheNames now ...