> No, but it is a design point of Dejavu.
> EAssociation -> HasA and HasMany? How is that different from Dejavu's
> UnitAssociation -> ToOne and ToMany?
Hum, I'll give Dejavu and SQLALchemy a better look, with sure. I should
be feeling like this guy now:
http://nerd.newburyportion.com/2005/11/ev
[EMAIL PROTECTED] wrote:
> > So why tell us? What are your ideas? What does your design do that the
> > others don't?
>
> Basically, the API I exemplificated in the first exemple. My initial
> idea was to have a way of turn alread designed objects into persistent
> ones. This is not the goal of SQL
> So why tell us? What are your ideas? What does your design do that the
> others don't?
Basically, the API I exemplificated in the first exemple. My initial
idea was to have a way of turn alread designed objects into persistent
ones. This is not the goal of SQLObject, for example.
Other litle diff
[EMAIL PROTECTED] wrote:
> I have some ideas about a ORM design, but have no time to start its
> development.
> I used SQLObject, Django's Model, and looked at SQLAlchemy and Dejavu,
> an readed some thread in the last year or so.
Wouldn't it be better to try and make the relationel model directly
[EMAIL PROTECTED] wrote:
> I have some ideas about a ORM design,
> but have no time to start its development.
So why tell us? What are your ideas? What does your design do that the
others don't?
Robert Brewer
System Architect
Amor Ministries
[EMAIL PROTECTED]
--
http://mail.python.org/mailman/
I have some ideas about a ORM design, but have no time to start its
development.
I used SQLObject, Django's Model, and looked at SQLAlchemy and Dejavu,
an readed some thread in the last year or so.
Here is an example:
#from EnhancedOcject.all import *
from EnhancedObject.core import EObject, EType
