Hi, I'm writing a small Seaside/Magma application and I'm using OrderedCollection and MagmaCollections.
The application works fine. But when I take a look in the objective- file with a text editor I noticed that a removed object remains in the objective-file.
Here are some code snippets for adding an object: issue ifNotNil: [self session commit: [self model add: issue]]
and for removing: remove: anIssueObject self session commit: [self model remove: anIssueObject]
Is this normal or do I anything wrong? Can I manually or automatic remove/collect old and unused objects?
Kind regards Robert
Hi Robert, it's true. Once a buffer for an object is allocated in the "objects" file, that space remains allocated until the next compress with MagmaCompressor.
On 9/2/07, Robert Schwarz r.schwarz@blackstream.at wrote:
Hi, I'm writing a small Seaside/Magma application and I'm using OrderedCollection and MagmaCollections.
The application works fine. But when I take a look in the objective- file with a text editor I noticed that a removed object remains in the objective-file.
Here are some code snippets for adding an object: issue ifNotNil: [self session commit: [self model add: issue]]
and for removing: remove: anIssueObject self session commit: [self model remove: anIssueObject]
Is this normal or do I anything wrong? Can I manually or automatic remove/collect old and unused objects?
Kind regards Robert _______________________________________________ Magma mailing list Magma@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/magma
magma@lists.squeakfoundation.org