Funny you should introduce this feature... I've been thinking about demonstrating a "cable database" application at the office - a tool to record what's on either end of a cable in a large laboratory installation, (e.g. DAQ board 1 <-- (cable) --> * Network switch) and this could just be more pleasing on the eye when viewing the switch's cable collection.
Thanks! On 15 Feb 2013 at 17:33, Dan Haywood wrote: > Hi folks, > > Just wanted to let you know of a small but useful enhancement as to how the > Wicket viewer renders parented tables. > > To explain (and this is taken from the ticket, [1]): > > ~~~ > Suppose we have a bidirectional many:many, eg Customer <->* CustomerAddress > *<-> Address. > > The CustomerAddress "link" entity has references back to both Customer and > Address. > > When viewing the Customer, we would like the parented table showing the > addresses collection (of CustomerAddress) to show the Address property of > the CustomerAddress but not to show the parent Customer property. > > Conversely, when viewing the Address, we would like the parented table > showing the customers collection (of CustomerAddress) to show the Customer > property of the CustomerAddress but not to show the parent Address property.
