There is sample for an alternative technique (the one between "save the full image" and "sandstone".

I kind of ported the example for my own use by using� Fuel based saves.

http://www.smalltalkhub.com/#!/~philippeback/DripfeedIt/packages/DripfeedIt-Persistence

You may need the DripfeedIt-Domain package as well as it contains the domain objects (basic objects mind you).

Phil

On Mon, May 27, 2013 at 1:58 PM, Sven Van Caekenberghe <sven@stfx.eu> wrote:

Hi,

That is because `DataStream' and `SmartRefStream' are old serialisation technologies.
There is a port of SandstoneDB using Fuel (and FileSystem), AFAIK.
Look at the specific versions on SqueakSource.
I can see that the original author made commits as well, which is very good.

There is also http://smalltalkhub.com/#!/~gnaritas/SandstoneDb but I don't know how it is related.

Sven

On 27 May 2013, at 13:46, Bahman Movaqar <Bahman@BahmanM.com> wrote:

> What is the correct way to install `SandstoneDb' in Pharo 2.0? �With the
> approach Pharo book takes[1], Pharo complains about two other packages
> to be installed as well: `DataStream' and `SmartRefStream'.
>
> TIA,
>
> [1] http://book.pharo-project.org/book/PharoTools/SandstoneDB
> --
> Bahman Movaqar �(http://BahmanM.com)
> ERP Evaluation, Implementation, Deployment Consultant

--
Sven Van Caekenberghe
Proudly supporting Pharo
http://pharo.org
http://association.pharo.org
http://consortium.pharo.org