News for hackers. Stuff that matters.
Re:Database development mistakes made by application developers by jfb on Monday December 13, 2010 @11:18AM (#2000904)
ON UPDATE CASCADE. Tis a pity it's not more widely implemented.
Re:Database development mistakes made by application developers by jasonlotito on Monday December 13, 2010 @01:05PM (#2001366)
Which does nothing for anything utilizing the resource itself outside the database. I'm not referring at all to keeping the database consistent. Having something you can always refer to to grab the same data is invaluable.
Re:Database development mistakes made by application developers by jfb on Monday December 13, 2010 @02:18PM (#2001623)
Fair enough. I'm more worried about database consistency -- it's just the way I roll, I guess.
Re:Database development mistakes made by application developers by jasonlotito on Monday December 13, 2010 @03:19PM (#2001827)
I'm all for database consistency. It's just not only database consistency that I'm worried about. I've just been burned by keys that were also data before. Having keys that aren't related at all to the data just hurts a few sensibilities and a few individuals sense of calm. =)
Re:Database development mistakes made by application developers by Devilboy on Monday December 13, 2010 @11:14PM (#2003097)
There are limits to even this. For example, you may have a table referencing itself (e.g. for tree structures) and on most systems you can't cascade updates. Also if your key is used in lots of other tables the cascade will become expensive.