Databases and text file usages

[khortez]

Originally Posted by cbk1994

Imagine you wish to find a list of all players in a certain guild. If you store the guild as a clientr variable (like clientr.guild=Vimes), then if you wanted to list all players in Vimes, you need to search every player who has ever logged on to the server. (This is impractically slow for most uses.)

If you store it in a text file or DB NPC, you could instead store an array guild.Vimes=cbk1994,Seeya and easily get that list.



You could, but beware problems which might result in inconsistent data between the two. Imagine you open a player's attributes via RC, they join a guild, then you save their attibutes. The DB NPC will have been updated, but not the player flags. Having a single source of data helps to keep things consistent and prevent subtle bugs.

Ah, I think I understand that. Thanks everyone

[MysticalDragon]

Originally Posted by khortez

Ah, I think I understand that. Thanks everyone

Don't use DB NPCs to store guild data, later on you will regret that decision.

[Tim_Rocks]

Originally Posted by MysticalDragon

Don't use DB NPCs to store guild data, later on you will regret that decision.

Yeah, use SQL. Works wonders for guild related system. It's convienant especially when players are offline. If you want to edit a players rank, remove them, or send invites. Just update a row in your SQL database.

[khortez]

Originally Posted by Tim_Rocks

Yeah, use SQL. Works wonders for guild related system. It's convienant especially when players are offline. If you want to edit a players rank, remove them, or send invites. Just update a row in your SQL database.

If SQL is the best way.. My only question would be, where would I begin learning it? Chompy gave me his source. but if anyone has other sources Id be happy to look at them all

[cbk1994]

Originally Posted by MysticalDragon

Don't use DB NPCs to store guild data, later on you will regret that decision.

Perfect is the enemy of the good. Even better to design your code so you can swap out the implementation easily, should you want to, in the future.