Thanks for the answer Rob! The intention was to avoid the the explicit definition of a join table in the fixtures, like it is possible since some months. See 'Let‘s make the HABTM fixture go away. ' in http://api.rubyonrails.org/classes/Fixtures.html
For your approach: I will put the omap into a roles_users.yml file, right? Regards, Peter. On Nov 23, 11:46 pm, Rob Biedenharn <[EMAIL PROTECTED]> wrote: > On Nov 23, 2008, at 5:22 PM, Peter wrote: > > > > > > > Hmmh, > > > even after cleaning up the roles_users (without timestamp) it does not > > work (Hint from [1]) > > Tried out different order of fixture importing -> nothing helps. > > > So, I switched to the old way to define fixtures [2] and it works :-) > > > Regards, > > Peter. > > > [1] > >http://groups.google.com/group/rubyonrails-talk/browse_thread/thread/... > > [2] > >http://railsforum.com/viewtopic.php?id=50 > > This is the only message I've looked at, but can you turn the join > table's fixture into an ordered map: > > --- !omap > - first: > id: "1" > role_id: "1" > user_id: "1" > - second: > id: "2" > role_id: "1" > user_id: "2" > > -Rob > > Rob Biedenharn http://agileconsultingllc.com > [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
