DragonPrime - LoGD Resource Community
Welcome Guest
  • Good afternoon, Guest.
    Please log in, or register.
  • October 19, 2017, 02:35:19 PM
Home Forums News Downloads Login Register Advanced Search
* * *
DragonPrime Menu
Login
 
 
Resource Pages
Search

Pages: [1]   Go Down
  Print  
Author Topic: db_prefix obligatory?  (Read 2629 times)
0 Members and 1 Guest are viewing this topic.
Jason
Guest
« on: January 20, 2005, 01:47:47 PM »

That's my question. Do I have to add db_prefix to all my sql statements? If yes, why?
Logged
Arune
Member
Mod God
*****
Offline Offline

Posts: 718


Arune Vai - khatfield


View Profile WWW
« Reply #1 on: January 20, 2005, 02:34:35 PM »

No you don't unless you are using database prefixes.

Now if you plan to write a module and release it here, with portability in mind it would be best to use db_prefix in your SQL calls so that it could be used by everyone.

Logged
Jason
Guest
« Reply #2 on: January 20, 2005, 02:37:53 PM »

Who would encounter problems if I don't?
Logged
Arune
Member
Mod God
*****
Offline Offline

Posts: 718


Arune Vai - khatfield


View Profile WWW
« Reply #3 on: January 20, 2005, 02:41:23 PM »

People with database prefixes..
Logged
Jason
Guest
« Reply #4 on: January 20, 2005, 02:43:41 PM »

*g* Okay, I'm ignorant. What does this mean?
Logged
Dannic
Guest
« Reply #5 on: January 20, 2005, 05:38:40 PM »

that means if your tables are prefixed with something other than nothing.

An example would be the table called accounts.  It is accounts without a prefix.  With a prefix you could make it logd_accounts.  logd_ is the prefix.

If you don't take the prefix into account when you make tables for modules then it would be of limited use.  Those who use table prefixes would not be able to use it and you would get lots of complaints. Smiley
Logged
Jason
Guest
« Reply #6 on: January 20, 2005, 05:52:21 PM »

Thanks, then it's absolutely necessary.
Logged
Sichae
iMod God
SVN Users
Mod God
*
Offline Offline

Posts: 3458


If ya didn't get it by now... you're hopeless...


View Profile WWW
« Reply #7 on: January 21, 2005, 09:48:17 AM »

Thanks, then it's absolutely necessary.

Not entirely, just ... oh, let's provide an example:

Mr Sando has a module that he runs only on his server ... he doesnt need to have the db_prefix capability, as long as his server does not have db prefixxing, and he does not intend to release it anywhere else.

So, kinda, db prefixxing is needed, but only on a larger scale then a private server *cough Strider cough*
Logged

If you didn't understand anything in the above post, don't try to attempt anything suggested.

Pages: [1]   Go Up
  Print  
 
Jump to:  


*
DragonPrime Notices
Version 1.1.2 is the current supported version and is available for download.

Support Us
No funds raised yet this year
Your help is greatly appreciated!
Recent Topics
DragonPrime LoGD
Who's Online
14 Guests, 0 Users
Home Forums News Downloads Login Register Advanced Search