New
#31
Ugh, RPG. Then again I'm a big fan of LISP so....
Can anyone Explain how this is Possible?
-
-
New #32
-
New #33
Whenever I've done that, it always comes back and bites me in the arse.PS - I always though it was better to just get rid of the offending data so it doesn't confuse you, plus, you gain all that extra space back! Bigger plus, you can get rid of the evidence of your short-sightedness! Who cares if you hosed referential integrity - it's overrated anyway. Also, make sure you use business data that can change as part of your primary key - makes it easier to find those offending rows you want to get rid of.
As for storage space, it used to be a problem years ago, but technology has finally caught up in the storage arena. Our databases aren't that big at work any ways, but I can certainly understand extreme instances such as the company Visa might have.
For the primary key, meh... I never use that column of data. It's just there for the SQL server to keep track of its own thing, hehehe. I always run my own ID column to track records to know sequentially which one is in what order.
-
New #34
Oh, PULEEZE! You can't seriously think I was serious about that! Three tongues sticking out? A veritable list of stupid things to do? I feel insulted!
-
Posts : 397 6x W2K8 R2 (x64), 6x W7 7600 (x64), 2x Gentoo (x64), 1x Ubuntu 9.04 (x64), 1x pfSense (FreeBSD)New #35
I assumed you were joking but it is honestly hard to tell. One developer I worked with swore by reusing database records as to not incur the hit of insert a new clustered index. He would instead take an inactive record and overwrite the non-index fields. He didn't keep his job long.
Myself....I'm a fan of GUID as primary keys with secondary indexed natural keys when appropiate.
-
New #36
Ooops, sorry.
<hides in corner now, not able to tell when DJG was joking>
Sorry, it wasn't you... your humor was so on target that I've actually heard those words before, hehehe.
-
New #37
I think most DB designers that have a fair understanding of the infrastructure they work in pretty much agree on common sense things. Like not use the SSN as the primary key for employee records, because typos do happen, and you can't change a PK (at least not easily).
Hey, no worries mate. You can come out of the corner.
-
New #38
i dont understand any of that junk
but according to PCwizard, i have a secret duel core processor, that i never knew about. and get this, it runs @ -0.999324741Mhz ... awesome?
-
New #39
Geek speek, nerd werds. Bit heads.
You can always tell a programmer, you just can't tell him much.
-
Posts : 2,899 Windows 7 Ult x64(x2), HomePrem x32(x4), Server 08 (+VM), 08 R2 (VM) , SuSe 11.2 (VM), XP 32 (VM) Thread Starter
.
Quote
?.
the quote of the day...
Related Discussions