Re: [PhillyOnRails] Foreign Key Constraint war stories?

[Aaron Blohowiak <aaron@aaronblohowiak.com>]

Changing your database structure to fit your development framework is  
not usually a good idea. Since your database is responsible for your  
data's integrity, you should put as much validation and safeguards as  
you can into it. Learn to work around (or, hopefully, fix and submit  
your upgrades to) rails' fkc rough spots.

OR

Dude, rails and FKC don't jive. Having them in your database is  
really repeating yourself which you shouldnt want to do -- your tests  
should be validating all of your code anyway. the only time it would  
be super necessary is if you have multiple apps hitting the same db  
and you doubt their ability to respect your data.

OR,

Check out:

 http://www.robbyonrails.com/articles/2005/08/18/active-record-i-3-u- 
but-i-still-trust-my-database-server-a-tiny-bit-more


Aaron Blohowiak



On Feb 28, 2006, at 11:37 PM, Mike Zornek wrote:

> Anyone here have any war stories about using FCK and Rails. I think  
> I'm
> writing a few of my own tonight and my boss (who really likes FKC) is
> suggesting we drop them since Rails (via DHH) doesn't support them  
> very
> well.
>
> Support in this context is probably not the right word -- depending  
> on you
> model relationships it feels more like Rails is punishing you for  
> using FKC.
>
> Anyways, I'm curious.
>
> ~ Mike
> --
> Work: http://ClickableBliss.com
> Play: http://MikeZornek.com
>
>
> _______________________________________________
> talk mailing list
> talk@phillyonrails.org
> http://lists.phillyonrails.org/mailman/listinfo/talk

_______________________________________________
talk mailing list
talk@phillyonrails.org
http://lists.phillyonrails.org/mailman/listinfo/talk