Coding advise about adding to a db column?

[Mr Blunt]

Thank You MarcoH64!!

Question 101
Now that I'm using my own table, are there any restrictions for field names, and in fact the short the better, correct?? Only point is to maybe make them friendly enough so coders understand the code, right? Like for example 'ip' would be better than 'ipaddress' ... providing of course that I pass all my arrays & variables correctly ..... OR ..... do coders making their own tables typically try to use the exact same field names as vbulletin so coders don't have to track down and/or think of how the variable got passed?? Another good example that I'd like to change is 'fileid' instead of the long 'attachmentid' .... OR ..... Are you guys saying that I really should change ALL field names to be unique names like real short 'dl', 'uid', 'uname', 'fid', 'fname', date, ip, altip


Question 102
So about the prefix...
You and Dream said:

Originally Posted by MarcoH64

It is always a good idea to prefix you fields (and tables) with something, so you know you won't get any conflicts.

Are you guys saying should I do something like split that INTO a "prefix.name" like "who.downloaded"?

And if so ... and I understand this right ... this would be in addition to the prefix declared in a user's config ... meaning my db calls would be like:

FROM " . TABLE_PREFIX . "who.downloaded


And if all that is true .... is "who" technically a bad choice for a prefix meaning I should make it something extremely arbitrary such as:

FROM " . TABLE_PREFIX . "blunts.whodownloaded