By KenDowns
via database-programmer.blogspot.com
Published: Jan 15 2008 / 08:45
You cannot make a tight and efficient application by trying to force every table into your database to use the same kind of primary key. In this entry I present the various rules of thumb I have worked out in 15 years in the field, I hope you find them helpful!
Comments
planetmcd replied ago:
@akitaonrails,
I found the piece to be quite cogent, I'm curious as to what you found wrong that prompted your down vote. I enjoy your blog so I was curious if you'd mind sharing.
Kenneth Downs replied ago:
As a follow-on to this question, I'm curious as to why he posted a comment on my blog, but then voted it down. A down vote presumably means "don't read" but then why read through it and comment on it?
planetmcd replied ago:
I can't speak for him, but I know I don't vote for something up or down unless I read it. And I know that just because I disagree with something, it doesn't mean I can't learn something from a friendly disagreement about a tech point. Its a good way to learn or to at least sharpen you're reasoning.
It's a limitation of dzone, which I believe they are aware of, that down voting is vague and could mean different things to different people, even different things to the same person at different. It can mean "I don't like this article", "I don't agree with the content of this article"; or "that &*%&^ took my lunch money when I was six, so they're never going to get an upvote from me" or sadly, "that article has a buzzword that I always vote down"
I sent him an email to ask him why since I found your article to be match with much of my experience, particularly when working on cross application databases.
dzonelurker replied ago:
half knowledge
Voters For This Link (15)
Voters Against This Link (3)