[Twisted-Python] enterprise.row and two-way relationships

Ken Kennedy kkennedy at abelard.kenzoid.com
Sun Oct 20 21:08:17 EDT 2002

On Sun, Oct 20, 2002 at 05:49:37PM -0500, Justin Ryan wrote:
> > Ah! Ok...now I'll show my lack of attention. I didn't pay attention to
> > the twisted.enterprise.ROW reference!
> > 
> > Well...the row stuff looks pretty wonky to me *grin*, but since I want
> > to understand it as well, we can figure it out together. 
> admittedly, it does.. I'm embarrassed to admit that I'm currently using
> a pretty lame db access method..

As of now, I'm leaning towards using twisted.enterprise without
t.e.row...except purely for learning purposes. Just this simple
example of yours shows how quickly object <-> relational model
mappings can get tricky. But learning about it should be interesting

> > able to talk apples to apples...
> I've got a few more fields in the contact table, but we can work with id
> and name..
> If you check the other reply to my post, I tried the create view method
> and it seems like it will work,

Yeah...I read it. That was my thought as well...use a view to flatten
out two of the objects into one. I'm trying to think of tweaking that
might help simplify the situation there. Some databases have
functionality that might enable you to use one denormalized view and
rewrites on the db backend that would peform the updates properly
depending on the table. But that functionality would be in the
database, so it would be implementation-specific. 


More information about the Twisted-Python mailing list