Master / detail object relationships

[MadDawg]

Working in .Net, but I suppose the question applies to any OO language

If you've got a master/detail relationship (say Order and OrderLine)
and the detail object needs info from the master (e.g. customer discount type) what's the best way of propagating the information? I started by passing the values as parameters to the constructor, but it's kinda snowballed, and I'm passing about 10 things now.
Passing the Order object to orderLine doesn't seem right either.
What options are there? I could stick all the parameters in a struct I guess?

TVM

[Ketchup]

Working in .Net, but I suppose the question applies to any OO language

If you've got a master/detail relationship (say Order and OrderLine)
and the detail object needs info from the master (e.g. customer discount type) what's the best way of propagating the information? I started by passing the values as parameters to the constructor, but it's kinda snowballed, and I'm passing about 10 things now.
Passing the Order object to orderLine doesn't seem right either.
What options are there? I could stick all the parameters in a struct I guess?

TVM

Try a fluent interface

[Kanye]

I think passing the Order to the OrderLine is fine - acessing attributes from the order is better than trying to use some structure or variables to keep data in sync between the order and it's lines.

[VectraMan]

I think passing the Order to the OrderLine is fine

WHS. If you want to be more object oriented about it, you could define an interface that the Order object implements and pass a reference to the interface into your OrderLine object. That way they're less tied together, and the detail object won't have full access.

If it was C++, you'd then have a circular reference problem to deal with.

[MadDawg]

Cheers - appreciated.