durusmail: durus-users: 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
OODB vs SQL
David Binger
2005-10-10
On Oct 10, 2005, at 9:12 AM, Rodrigo Dias Arruda Senra wrote:

> I wonder if C.J.Date mentioned anything about databases for storing
> large dense graphs in that book ?

He doesn't talk about that in this book.

> Just to give an example, the Brazilian Government is sponsoring a
> project
> to build an AI system to double-check tax declarations. We are
> talking about
> 200 million people. One of this project goals is to examine the
> relationship
> graph (family, employment, etc) trying to detect fraud. Even though
> that can be
> modelled in a Relational DB, I'll investigate if an OODB with an
> appropriate
> storage would give better performance. My instinct says yes.

I'd be interested to hear about the storage design for a database of
that size.

> By the way, I helped another federal project to build a Python
> desktop app to
> record info from more than 150.000 public schools. While working
> off-line,
> such app used Twisted + **Durus**.  But unfortunately, due to the
> rampant corruption
> unveiled recently, the project is in the freezer. If it ever gets
> out I'll let
> you know.

Good luck with the thaw.

reply