[Seaside] Re: OBject databases

[Frank Mueller]

Hi Wouter,

that's really funny. It seems that I'm a bit too late. I'm currently devloping something
similar called SOS. You'll find some more information under
http://wiki.tideland.biz/wiki/SosConcept. Through the usage of strategies and a command
pattern it will be able to use almost any database.

Right now I'm porting my Squeak prototype to VW, then I'll finish the first strategy
implementation for PostgreSQL. Commit and rollback will also be functional as multiple
sessions. Only for the thread safeness I've got to learn more about how they are handled
in Smalltalk / VW. Doing that in Java was relative simple.

mue

> I've just published the bundle 'OO Storage' to the public repository
> under the GPL. It is basically a simple OO database using a SQL server
> for storage (currently only PostgreSQL).
>
> The main ideas about it are:
>  - It should store any kind of smalltalk object.
>  - You don't have to write any descriptors for things you like to store.
>  - OO Storage only uses the database for storage/transaction support,
> so don't look at how the database looks.
>  - Transactions are the way to commit data to the database.
>  - The database is actually a big dictionary so you can use 'session
> rootAt: #myObjects' to retrieve and 'session rootAt: #myObjects put:
> myObjects' to save/ retrieve
>
> Currently supported:
>  - Different sessions which can have a different state.
>  - Commits
>  - Change propagation to other sessions
>
> Currently not supported:
>  - Tread safeness
>  - Rollbacks
>  - Different sessions in different images
>  - Anything different than VisualWorks (it uses the immutability
> mechanism) / PostgreSQL
>  - bugfreeness
>
> Wouter

-- 
**
** Frank Mueller / Oldenburg / Germany
**
** frank at mweb.de / http://frank.mweb.de
**