Re: [Zope3-Users] IRelationshipMapper
On Jul 10, 2006, at 10:09 PM, Gary Poster wrote: Jim built the nice-n-simple zc.extrinsicreference package for a good way to make back- references to Python references. Apologies: Benji York built the nice-n-simple zc.extrinsicreference package. :-) Gary ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] IRelationshipMapper
On Jul 10, 2006, at 9:42 PM, Pete Taylor wrote: ... Still, I'll look at it again, and at the zc.relation module that David mentioned earlier, and see if there's already work that's been done in this area. zc.relationship. :-) Slog through it: the relationship index is an engine that could do the heavy lifting for what I understand you want from a quick read of your blog. A nice "intro to zc.relationship" blog entry or doctest would be a much-appreciated contribution, btw. The current README is a bit overwhelming. http://svn.zope.org/zc.relationship/trunk/src/zc/relationship/ I don't know about schooltool's relationship stuff--I can't use it because of licensing, so didn't look at it. It may or may not be able to do what you are looking for too. Finally, don't forget Jim's lament: he builds a nice object database, with direct pointers, speed, and nice clear Pythonic spelling, and we go off and build extrinsic relationship stuff that makes the ODB try to be a second-class RDB. :-) Sometimes it makes sense, when both sides of a relationship are extrinsic to the objects involved, but other times it's nice to remember that a direct Python reference is the simplest way to make an intrinsic relationship. Jim built the nice-n-simple zc.extrinsicreference package for a good way to make back-references to Python references. Gary ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] IRelationshipMapper
Alek, That may be the case, though looking at schooltool.relationships, it does manage a few kinds of specific relationships, but it's not as generic as I was proposing... the schooltool relationships module is specifically geared toward that application space, not a more generalized solution. Still, I'll look at it again, and at the zc.relation module that David mentioned earlier, and see if there's already work that's been done in this area. Thanks! Pete Isn't this IRelationshipManager similar to what schooltool.relationship provides? -- "All guilt is relative, loyalty counts, and never let your conscience be your guide." - Lucas Buck, American Gothic ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] IRelationshipMapper
Pete Taylor napisał(a): It is basically a statement of a way to manage non-containment relationships between ZODB persisted objects in a way that should not necessitate object-intrusive code. However, There may be complexities that I've neglected, or other extant solutions for this same kind of problem in Zope3 that I'm just unaware of. Isn't this IRelationshipManager similar to what schooltool.relationship provides? ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] IRelationshipMapper
Hi Pete. Isn't this what relationship does or could do? http://svn.zope.org/zc.relationship/trunk/src/zc/relationship Regards, David Pete Taylor wrote: Hi all, The other day I had an interesting idea for managing complex inter-object relationships in Zope3 in a way I haven't seen done before. I threw a blog up about it so I wouldn't forget it when the idea struck me (things I don't write down, I tend to forget, no matter how seeming important at the time). I wasn't going to mention it on the list immediately, because as with many ideas I get enthused about, after a day or two of thinking, I realize one of many different things about the idea. The realizations regularly include, but are not limited to, a) that it has been done already, b) that it doesn't solve a problem I'm likely to have more than once, or c) that it introduces more complexity into a given system than the original problem space contained. So, I waited on this one. And a few weeks later, it still seems like an interesting idea. But what I'd like is some commentary and feedback from other people in the Zope community, especially from anyone who may have pondered (or solved!) this kind of thing before. The post is located here: http://baldtrol.blogspot.com/2006/06/irelationshipmapper.html It is basically a statement of a way to manage non-containment relationships between ZODB persisted objects in a way that should not necessitate object-intrusive code. However, There may be complexities that I've neglected, or other extant solutions for this same kind of problem in Zope3 that I'm just unaware of. Any suggestions, comments, or thoughts on how to improve on this design would be more than welcome... I would like to start working on an implementation of this idea... I've done something like this on a smaller scale already, but would be very interested in hearing thoughts on this before I undertake the larger project. Thanks all! Pete ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] IRelationshipMapper
Hi all, The other day I had an interesting idea for managing complex inter-object relationships in Zope3 in a way I haven't seen done before. I threw a blog up about it so I wouldn't forget it when the idea struck me (things I don't write down, I tend to forget, no matter how seeming important at the time). I wasn't going to mention it on the list immediately, because as with many ideas I get enthused about, after a day or two of thinking, I realize one of many different things about the idea. The realizations regularly include, but are not limited to, a) that it has been done already, b) that it doesn't solve a problem I'm likely to have more than once, or c) that it introduces more complexity into a given system than the original problem space contained. So, I waited on this one. And a few weeks later, it still seems like an interesting idea. But what I'd like is some commentary and feedback from other people in the Zope community, especially from anyone who may have pondered (or solved!) this kind of thing before. The post is located here: http://baldtrol.blogspot.com/2006/06/irelationshipmapper.html It is basically a statement of a way to manage non-containment relationships between ZODB persisted objects in a way that should not necessitate object-intrusive code. However, There may be complexities that I've neglected, or other extant solutions for this same kind of problem in Zope3 that I'm just unaware of. Any suggestions, comments, or thoughts on how to improve on this design would be more than welcome... I would like to start working on an implementation of this idea... I've done something like this on a smaller scale already, but would be very interested in hearing thoughts on this before I undertake the larger project. Thanks all! Pete -- "All guilt is relative, loyalty counts, and never let your conscience be your guide." - Lucas Buck, American Gothic ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
