From: Vsevolod (S. I. <si...@cs...> - 2004-02-16 23:36:40
|
> Obviously, I'm biased :-), but I would rather see effort put into movin= g=20 > to this more general structure rather than adding onto the existing mor= e=20 > limited one. I'm with you. I have already been bitten by the problem of manually=20 managing the order of saving members of composite objects (ie, has_a=20 members have to be saved before the parent object, but links_to members=20 have to be saved after it) - I'd rather specify it in the configuration. > Actually, no. I used the three classes X, A and B just to define some=20 > minimal notation that I could use to talk about all of the above=20 > relationships. For simple one-to-one and one-to-many relationships, jus= t=20 > look at X and A (pretend you don't have B). See the first 3 examples at= =20 > the end of the first post. Gotcha. Chris, what do you think? With my current amount of free time I could expect to implement this by summer. Simon --=20 Simon (Vsevolod ILyushchenko) si...@cs... http://www.simonf.com The unknown is honoured, the known is neglected - until all is known. The C=FA Chulaind myth |