[Pharo-project] Pharocast ContactManager using SandstoneDb

Bernat Romagosa tibabenfortlapalanca at gmail.com
Wed May 4 17:01:26 CEST 2011


Also, images can get corrupted, crash, etc.

2011/5/4 Miguel Cobá <miguel.coba at gmail.com>

> 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
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gforge.inria.fr/pipermail/pharo-project/attachments/20110504/3330d5cc/attachment.htm>


More information about the Pharo-project mailing list