mario ruggier wrote:
>
> In addition to this, I think what might turn on a little media spotlight
> on Durus is some sort of scenario comparison... that addresses in some
> ways each issue that keeps people away from OODBs and stick with SQL. A
> task / data model that lends itself well for OO... Compare at least 3
> cases: pure OO, using an ORB, pure SQL. This is of course a rather big
> job, but the results could become very publicized... besides being very
> interesting for all of us. It would also lead to an interesting
> presentation at pycon. A dbshowdown, à la pyweboff... I do not know if
> anyone here has an idea of what an appropriate task (and reasonably
> implementable) might be to base such a comparison on. Implementations
> for each case could probably be delegated out...

I'd be happy to create the Schevo version of this comparison
application.  As an example of that, we took the TurboGears tutorial,
which uses SQLObject, and rewrote it to use Schevo.  You can see what
that looks like here:

http://docs.schevo.org/trunk/extensions/gears/wiki.html

I think there are other application domains that would do a better job
of showing pure database functionality than this one.  How about a
simple ToDo manager?  Or maybe one of the more mature SQL products has
an example application that we could rewrite as an OODB app?

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