| 1 |
On Wednesday 17 August 2005 14:36, Grobian wrote: |
| 2 |
> From a database point of view, it is evil to duplicate values in an |
| 3 |
> automated manner, just use a foreign key for such purposes. In other |
| 4 |
> words, avoid duplication. If such bash function is a common tool then |
| 5 |
> -- apart from wondering why it isn't part of the default suite -- this |
| 6 |
> anti-duplication constraint is being broken massively. I like Mike's |
| 7 |
> idea, because it deals with data redundancy and basically uses this |
| 8 |
> 'foreign key' for the changelog. |
| 9 |
There's a big difference: a database is intended to be used by apps, |
| 10 |
changelogs and commit logs are intended to be used by humans. |
| 11 |
|
| 12 |
Example? When you go in a forum you don't see the foreign key referring to |
| 13 |
users, to forums, to replies ... you see the actual data. |
| 14 |
Same for webpages. |
| 15 |
|
| 16 |
I still find a natural ChangeLog simpler to look at instead of using cvs log. |
| 17 |
|
| 18 |
-- |
| 19 |
Diego "Flameeyes" Pettenò |
| 20 |
Gentoo Developer - http://dev.gentoo.org/~flameeyes/ |
| 21 |
(Gentoo/FreeBSD, Video, Gentoo/AMD64, Sound, PAM) |
Archives