Reply to thread

Message

<blockquote data-quote="Fractalwave" data-source="post: 342607" data-attributes="member: 6399">That's why you end up limiting the implementation to what is commonly used. The problem with that is you also might end up with something that is so generic it can't handle some of the really great things that we love about the different systems.This is something that we have run into in a limited extent within Campaign Suite. You think something is unrelated but it isn't.You don't have to completely link all the pieces of the database. In other words, you can create an npc that's an elf, then delete the elf race. It doesn't matter because it picks up what it needs when you created it. The problem then becomes what happens later when you need that npc to have something else that is elf-only after a certain level and you inadvertently deleted the item or the race so it can't run a check.You can end up with a database that is not optimized and repeated information in different tables. Then you have to remember to update all the different tables and it potentially runs slower. So go for a happy medium, perhaps?</blockquote>

[QUOTE="Fractalwave, post: 342607, member: 6399"] That's why you end up limiting the implementation to what is commonly used. The problem with that is you also might end up with something that is so generic it can't handle some of the really great things that we love about the different systems. This is something that we have run into in a limited extent within Campaign Suite. You think something is unrelated but it isn't. You don't have to completely link all the pieces of the database. In other words, you can create an npc that's an elf, then delete the elf race. It doesn't matter because it picks up what it needs when you created it. The problem then becomes what happens later when you need that npc to have something else that is elf-only after a certain level and you inadvertently deleted the item or the race so it can't run a check. You can end up with a database that is not optimized and repeated information in different tables. Then you have to remember to update all the different tables and it potentially runs slower. So go for a happy medium, perhaps? [/QUOTE]

Verification