Triligon / Blog / Improvement for enhancedobjectrelation

Improvement for enhancedobjectrelation

« 
Previous entry
|
Blog
|
Next entry
 »

Gabriel Ambuehl

Wednesday 08 February 2006

I wonder if the following would be of any use:

Right now, we can do attribute -> contentobject links (and backwards, of course).

How about doing contentobject -> attribute and attribute -> attribute? All this would take is another field in the relation table (and persuasion of ez devs to integrate such in ez 3.8 which would be the hard part ;).

Another idea would be to add a "boolean" (I know MySQL doesn't support it per se) field that says it is actually a bidirectional link and then have both object's see it as their "own" relation as well as reverse relation!

Filed under: enhancedobjectrelation   eZPublish  

Comments

RSS Streams for comments: http://triligon.org/triligon/flexiblerss/rssexport/view/flexiblerss_children/nodeid/235

Gabriel

Use cases...

Not really, it's more a build and they will come thing ;)

There's one thing I could possibly use it for: forum subscriptions in my forum work via EOR fields. This is all nice and dandy BUT it means a forum can potentially have thousands of reverse related objects, thus somewhat obscuring other, non user related objects. If the users could be grouped under a subscriptions field, they wouldn't clog up the admin menu as much?

xavier

Example usage ?

Hi,

Do you have a specific example in mind ?
On an abstact level, I like your idea as it solves well an abstract problem, but I can't think of a (real life) case where I would need it.

X+