Long column names...Performance issues?

#**101**

On 5 Dec., 21:07, Ed Prochak <edproc... (AT) gmail (DOT) com> wrote:

Quote:

You had me until the suggestion that all tables should have surrogate
ID primary Keys. Otherwise I think your suggestions look good.

Several years ago I was more categoric about these things, today I'd
say that wahtever suits one better is OK, however I personally stick
to surrogates for new apps anyway

Gints Plivna
http://www.gplivna.eu

#**102**

On 5 Dec., 21:07, Ed Prochak <edproc... (AT) gmail (DOT) com> wrote:

Quote:

You had me until the suggestion that all tables should have surrogate
ID primary Keys. Otherwise I think your suggestions look good.

Several years ago I was more categoric about these things, today I'd
say that wahtever suits one better is OK, however I personally stick
to surrogates for new apps anyway

Gints Plivna
http://www.gplivna.eu

#**103**

On 5 Dec., 21:07, Ed Prochak <edproc... (AT) gmail (DOT) com> wrote:

Quote:

You had me until the suggestion that all tables should have surrogate
ID primary Keys. Otherwise I think your suggestions look good.

Several years ago I was more categoric about these things, today I'd
say that wahtever suits one better is OK, however I personally stick
to surrogates for new apps anyway

Gints Plivna
http://www.gplivna.eu

#**104**

On 5 Dec., 21:07, Ed Prochak <edproc... (AT) gmail (DOT) com> wrote:

Quote:

You had me until the suggestion that all tables should have surrogate
ID primary Keys. Otherwise I think your suggestions look good.

Several years ago I was more categoric about these things, today I'd
say that wahtever suits one better is OK, however I personally stick
to surrogates for new apps anyway

Gints Plivna
http://www.gplivna.eu

#**105**

On 5 Dec., 21:07, Ed Prochak <edproc... (AT) gmail (DOT) com> wrote:

Quote:

You had me until the suggestion that all tables should have surrogate
ID primary Keys. Otherwise I think your suggestions look good.

Several years ago I was more categoric about these things, today I'd
say that wahtever suits one better is OK, however I personally stick
to surrogates for new apps anyway

Gints Plivna
http://www.gplivna.eu

#**106**

On 5 Dec., 21:07, Ed Prochak <edproc... (AT) gmail (DOT) com> wrote:

Quote:

You had me until the suggestion that all tables should have surrogate
ID primary Keys. Otherwise I think your suggestions look good.

Several years ago I was more categoric about these things, today I'd
say that wahtever suits one better is OK, however I personally stick
to surrogates for new apps anyway

Gints Plivna
http://www.gplivna.eu

#**107**

On 5 Dec., 21:07, Ed Prochak <edproc... (AT) gmail (DOT) com> wrote:

Quote:

You had me until the suggestion that all tables should have surrogate
ID primary Keys. Otherwise I think your suggestions look good.

Several years ago I was more categoric about these things, today I'd
say that wahtever suits one better is OK, however I personally stick
to surrogates for new apps anyway

Gints Plivna
http://www.gplivna.eu

#**108**

On 5 Dec., 21:07, Ed Prochak <edproc... (AT) gmail (DOT) com> wrote:

Quote:

You had me until the suggestion that all tables should have surrogate
ID primary Keys. Otherwise I think your suggestions look good.

Several years ago I was more categoric about these things, today I'd
say that wahtever suits one better is OK, however I personally stick
to surrogates for new apps anyway

Gints Plivna
http://www.gplivna.eu

#**109**

On 5 Dec., 21:07, Ed Prochak <edproc... (AT) gmail (DOT) com> wrote:

Quote:

You had me until the suggestion that all tables should have surrogate
ID primary Keys. Otherwise I think your suggestions look good.

Several years ago I was more categoric about these things, today I'd
say that wahtever suits one better is OK, however I personally stick
to surrogates for new apps anyway

Gints Plivna
http://www.gplivna.eu

#**110**

Gints Plivna wrote:

Quote:

On 5 Dec., 21:07, Ed Prochak <edproc... (AT) gmail (DOT) com> wrote:

You had me until the suggestion that all tables should have surrogate
ID primary Keys. Otherwise I think your suggestions look good.

Several years ago I was more categoric about these things, today I'd
say that wahtever suits one better is OK, however I personally stick
to surrogates for new apps anyway

That's a non-answer if I ever heard one. The design criteria for primary
keys are uniqueness, irreducibility, familiarity, stability and
simplicity -- not necessarily in that order. The criteria frequently
contradict one another requiring the designer to make tradeoffs.

Your attitude basically says you don't have a clue how to do real design
so you use a simplistic rule instead. Evaluating designs and
understanding design tradeoffs is central to what we do.