[Seaside] backing up data with gemstone/s

James Foster Smalltalk at JGFoster.net
Wed Jun 26 18:23:27 UTC 2013

See section 11.4, "Passive Object" on pages 238-39 of http://community.gemstone.com/download/attachments/6816862/GS64-ProgGuide-3.1.pdf?version=1 (available from http://community.gemstone.com/display/GSS64/GemStoneS+64+Documentation). The introduction describes the following:

"To archive your data, you can passivate objects themselves to a file. Objects representing your data are stored into a serialized, text-based form by the GemStone class PassiveObject. PassiveObject starts with a root object and traces through its instance variables, and their instance variables, recursively until it reaches special objects (instances of SmallInteger, Character, Boolean, SmallDouble, or UndefinedObject), or classes that can be reduced to special objects (strings and numbers that are not integers), creating a representation of the object that preserves all of the values required to re-create it. The resulting network of object descriptions can be written to a file, stream, or string."


On Jun 26, 2013, at 10:16 AM, Johan Brichau <johan at inceptive.be> wrote:

> Hi James,
> Can you maybe elaborate a bit on this 'passivate' method?
> Sounds interesting. 
> thx
> Johan
> On 26 Jun 2013, at 16:38, James Foster <Smalltalk at JGFoster.net> wrote:
>> It is also possible to export a subset (using a native method called "passivate" or something like SIXX) and import that subset into an existing repository.
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the seaside mailing list