> Of course, one should change their database infrequently and deliberately, I think this attitude leads to a lot of crappy code. It's "safer" just to add a bi

> Of course, one should change their database infrequently and deliberately, I think this attitude leads to a lot of crappy code. It's "safer" just to add a bit more to the application layer than to change the database, but do that enough times and you end up with a mess to compensate for a database design that doesn't model what it needs to. (Learned through experience).