> > Yes, I think you're right and going with Referential Integrity should > > be the way to go to make sure the rules are enforced at the DB level. > > Although, I still would like to know how I can accomplish what I was > > trying to do. > > With foreign key constraints. There is really no reason to do it any > other way.
But it would provide me with knowledge of Rails internals I don't have right now that might become useful in the future. > Yes, apparently you missed my announcement a couple months ago of my > fork of Foreigner with MS SQL Server > support:http://github.com/marnen/foreigner > The gem is available as marnen-foreigner. Thanks, will look into it. -- 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.
