2009/6/26 Dan Kubb (dkubb) <[email protected]>: > I was waiting for someone to ask for that before adding it back in :) > > I'm not sure :remote_name is the best name for it though, so if I did > add it back I'd probably support :remote_name, with a warning to use > the new option instead.
I know what you mean as I initially found it hard to get my head round what the remote_name option actually did when I first came across it. Been trying to think of something better but nothing too inspiring comes to mind - the best I can come up with is joined_as. > If you could file a ticket for this I would appreciate it. Bonus > points for a stand-along script demonstrating the problem -- it's much > easier for me to know if I've resolved the problem when I can see it > working by running a script. Done (ticket #928) - and many thanks again for the RC - I'm loving the new association code - it's allowed me to remove the hackish stuff I had in some of my models so they worked with 0.9.x. Ooh, and the target/source naming has really helped when looking through the dm source (I could never get my head round which was the parent and which was the child in 0.9.x). Cheers Rupert -- roovoweb.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DataMapper" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/datamapper?hl=en -~----------~----~----~----~------~----~------~--~---
