OODB basics
2005-10-08
Oleg Broytmann2005-10-08
Patrick K. O'Brien2005-10-09
David Binger2005-10-09
Patrick K. O'Brien2005-10-09
David Binger2005-10-09
Patrick K. O'Brien2005-10-09
Oleg Broytmann2005-10-09
David Binger2005-10-09
Oleg Broytmann2005-10-09
Oleg Broytmann2005-10-09
Patrick K. O'Brien2005-10-09
Oleg Broytmann2005-10-09
mario ruggierOODB vs SQL
2005-10-09
Oleg Broytmann2005-10-09
Patrick K. O'Brien2005-10-09
Oleg Broytmann2005-10-09
Patrick K. O'Brien2005-10-09
Oleg Broytmann2005-10-09
John Miller2005-10-09
Patrick K. O'Brien2005-10-12
mario ruggier2005-10-09
David Binger2005-10-09
Oleg Broytmann2005-10-10
Rodrigo Dias Arruda Senra2005-10-10
David Binger2005-10-11
mario ruggier2005-10-11
Rodrigo Dias Arruda Senra2005-10-11
A.M. Kuchling2005-10-11
Rodrigo Dias Arruda Senra2005-10-11
Roger E. Masse2005-10-11
Rodrigo Dias Arruda Senra2005-10-11
Roger E. MasseRe: OODB vs SQL
2005-10-11
Michael Watkins2005-10-11
Michael Watkins2005-10-11
Patrick K. O'Brien2005-10-11
Patrick K. O'Brien2005-10-11
David Binger2005-10-11
Patrick K. O'Brien2005-10-15
Patrick K. O'Brien2005-10-12
Michael Watkins2005-10-12
Patrick K. O'Brien2005-10-12
mario ruggier2005-10-12
Michael Watkins2005-10-12
Patrick K. O'BrienDemo application [was: Re: [Durus-users] Re: OODB vs SQL]
2005-10-13
mario ruggier2005-10-12
Patrick K. O'BrienRe: OODB vs SQL
2005-10-11
Michael Watkins2005-10-11
Rodrigo Dias Arruda SenraDurus basics
2005-10-09
Oleg Broytmann2005-10-09
David BingerRe: OODB basics
2005-10-13
Oleg BroytmannOODB vs SQL
Patrick K. O'Brien
John Miller wrote: > On Oct 9, 2005, at 12:45 PM, Patrick K. O'Brien wrote: > >> Oleg Broytmann wrote: >> >>> Thank you. Have I missed something important? >> >> >> Hmm. Tough question. I'm convinced that there is nothing in the >> Relational world that can't be achieved in an OODB with the exception of >> language independence. > > > What about relationships? I guess one thing I've not been able to > understand about OODBs is how to achieve relations like I can with > relational databases. Schevo introduces several things to achieve this. For one, every Entity class automatically gets a corresponding Extent class that manages instances of that particular Entity. Dealing with the Extent is like dealing with a Relational table. Next, a Schevo Entity has fields, which are like Python attributes but are actually instances of Field classes. One field class is an Extent Field, which supports a reference from one entity to another, in a child/parent or many:one relationship. These references are automatically indexed, referential integrity is enforced, and deletes of parents can be declared to be restricted (the default), cascade, or set the field to unassigned (kind of like an SQL NULL, but less evil). -- Patrick K. O'Brien Orbtech http://www.orbtech.com Schevo http://www.schevo.org Pypersyst http://www.pypersyst.org PyDispatcher http://pydispatcher.sourceforge.net