The difference is that saving the whole image is a longer operation that
just saving a couple records when they are directed to do so. In a image
with little activity this difference can be almost null but in a heavy
accessed image with a lot of data being created, the difference in times
is notorious.
Also, the image save is blocking AFAIK and during image saving the
responsiveness is greatly diminished.
Cheers
El mi��, 04-05-2011 a las 04:36 -0700, Jeff Gray escribi��:
--> Kind of on topic as you're talking about sandstone....Since all records are
> loaded at start up, is there an advantage of using sandstonedb for
> persistence over just saving the image?
>
> --
> View this message in context: http://forum.world.st/Re-Pharocast-ContactManager-using-SandstoneDb-tp3493449p3495214.html
> Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
>
Miguel Cob��
http://twitter.com/MiguelCobaMtz
http://miguel.leugim.com.mx