well the recornd number is i\only usefull if your going to use it. If
your databse is small (IE not too many fields) then worry more about
how it will be accessed so you can setup the correct keys. Poor keys
will kill performance more than anything else. You can normalize your
database until the cows come home but if you got crappy keys your dead
meat. It might not be noticable on a small databse but I'm used to
working with databases with millions of records and you'll notice it
for sure then. :)
*********** REPLY SEPARATOR ***********
On 9/6/99 at 1:23 AM Daniel de Young scribbled:
>Ok, I'm putting the final touches on my initial database table. I
need
>to do quite a bit more reading to learn what exactly I should include.
>I'm assuming I should include a record (or row) number that increments
>with each new entry. This database work is combating my job research
>time, but It's too much fun to just lay down!
>
>Thanks for all your suggestions so far. Brian, once I complete the
>database model I'll take a closer look at the code examples on your
>site, they look like they'll help a lot. If I don't take it a step at
a
>time, then I get sidetracked ;-) (I'm probably the only one).
>
>You guys are awesome,
>
>--
>Daniel de Young MCP+I, MCSE
>___________________________
>
>NT Network Support
>
>"If you can't make it good, at least make it look good." -Bill Gates
>
>Check it out... Joshua 24:15
>
>http://go.to/thehub
RaEl
Deepwell Quake Server admin
quakeadmin@deepwell.com ICQ#: 125581
http://rand.deepwell.com/
This archive was generated by hypermail 2b29 : Fri Feb 25 2000 - 14:29:07 PST