Issue 210 in glassdb: Programmatic access to Update...>Update GLASS

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

New issue 210 by [hidden email]: Programmatic access to  
Update...>Update GLASS
http://code.google.com/p/glassdb/issues/detail?id=210

The 'Update GLASS' functionality does one or two things that I don't want  
to do as part of Metacello, but are useful for GLASS (primarily smoothing  
over upgrade issues when and if they arise), but I don't think there is a  
clean API for doing an update from topaz and there should be ..

Updates:
        Blockedon: 235

Comment #1 on issue 210 by [hidden email]: Programmatic access to  
Update...>Update GLASS
http://code.google.com/p/glassdb/issues/detail?id=210

GsDeployer should handle this in some way

Updates:
        Labels: Milestone-1.0-beta.8.7

Comment #2 on issue 210 by [hidden email]: Programmatic access to  
Update...>Update GLASS
http://code.google.com/p/glassdb/issues/detail?id=210

(No comment was entered for this change.)

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

Comment #3 on issue 210 by [hidden email]: Programmatic access to  
Update...>Update GLASS
http://code.google.com/p/glassdb/issues/detail?id=210

Moving forward the update to a new version of GLASS doesn't require as much  
monkey business as upgrading from the older versions, so a simple Metacello  
version load should do the trick (with all of the GsDeployer dressing:  
autocommit, handling warnings, etc.). See GsDeployer class>>updateGLASSTo:

Name: ConfigurationOfGsMonticello-dkh.115
Author: dkh
Time: 03/24/2011, 11:23:49
UUID: d2b9bd8e-33b1-4500-9a2a-036c2cad105b
Ancestors: ConfigurationOfGsMonticello-DaleHenrichs.114