Issue 286 in glassdb: GsDeployer>>doBulkMigrate fails if there are more than 2000 classes ....

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

New issue 286 by [hidden email]: GsDeployer>>doBulkMigrate fails if  
there are more than 2000 classes ....
http://code.google.com/p/glassdb/issues/detail?id=286

for full story see  
http://forum.world.st/loading-new-code-base-stalls-and-fails-td3630967.html

If you run a bulkMigrate with more than 2000 classes, then second round of  
migrates wil fail with #rtErrAbortWouldLoseData because the first set of  
classes have already been migrated (and dirtied) ...

Need to to come up with a better way to structure the code ... a commit  
within the loop will probably do the trick, but if one is trying ot do the  
migrate in one transaction, that's not the best solution...

Updates:
        Labels: Milestone-1.0-beta.8.7

Comment #1 on issue 286 by [hidden email]: GsDeployer>>doBulkMigrate  
fails if there are more than 2000 classes ....
http://code.google.com/p/glassdb/issues/detail?id=286

(No comment was entered for this change.)

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

Comment #2 on issue 286 by [hidden email]: GsDeployer>>doBulkMigrate  
fails if there are more than 2000 classes ....
http://code.google.com/p/glassdb/issues/detail?id=286

fixed in GsMonticello 0.241 (dkh.131).

I structured things so that all of the instances are collected before  
starting the migration phase ... I created a temporary persistent  
collection that holds onto all of the instances lists and does commits as  
needed ... after the migration phase is completed, the temporary persistent  
collection is dereferenced ...