durusmail: durus-users: Re: OODB vs SQL
OODB basics
2005-10-08
2005-10-09
2005-10-09
2005-10-09
2005-10-09
2005-10-09
2005-10-09
2005-10-09
2005-10-09
2005-10-09
2005-10-11
2005-10-12
Re: OODB basics
2005-10-11
OODB vs SQL
2005-10-09
2005-10-09
2005-10-09
Re: OODB vs SQL
2005-10-10
Re: OODB vs SQL
2005-10-10
OT: Durus
2005-10-13
2005-10-13
2005-10-13
2005-10-09
2005-10-09
2005-10-09
2005-10-10
2005-10-11
2005-10-11
2005-10-11
2005-10-11
Re: OODB vs SQL
2005-10-11
2005-10-11
2005-10-11
2005-10-12
2005-10-12
2005-10-12
Demo application [was: Re: [Durus-users] Re: OODB vs SQL]
2005-10-13
Re: OODB vs SQL
2005-10-11
Durus basics
2005-10-09
2005-10-09
2005-10-10
2005-10-10
2005-10-10
2005-10-13
2005-10-13
2005-10-13
2005-10-13
Re: OODB basics
2005-10-13
Re: OODB vs SQL
Patrick K. O'Brien
2005-10-12
mario ruggier wrote:
>
> Patrick, could this be the basis of a comparison between various
> implementation scenarios? It is rather relational in nature though... if
> we define what the test application should do, then whoever wants can
> implement the test to those speces.

It will be an interesting start, but I don't think it will do a very
good job of showing what I consider to be the important features of
Schevo.  In the applications I'm currently creating with Schevo, I have
closer to 20 entity classes, almost all of which have calculated fields,
customized create/update/delete transactions, and fairly rich behavior.
 But I'll see what can be done with these two entities.  We might be
able to make up some business rules that flex these other areas.

--
Patrick K. O'Brien
Orbtech       http://www.orbtech.com
Schevo        http://www.schevo.org
Pypersyst     http://www.pypersyst.org
PyDispatcher  http://pydispatcher.sourceforge.net

reply