1

Closed

Need better handling of NPCs

description

currently, the NPC is stored as a regular pilot involved. This is, unfortunately, causing some problems on parsing, because there is a foreign key to the ekbPilots table.
 
the current option is to remove the foreign key relationship (or at least the enforcement of referential integrity). Other options:
 
  1. Add NPC pilots to the pilot table on parsing. This could cause an issue because it will pollute that table with unneeded data.
  2. Add a column to the ekbInvolved table for NPC data. This would require refactoring some existing code.
  3. Add an ekbNPCInvolved table. This is probably the best bet (and would require the most amount of work).
Closed Dec 28, 2009 at 4:43 AM by robaticus
Implemented in current release.

comments

robaticus wrote Dec 28, 2009 at 4:42 AM

Finally decided to go with choice #2. Overall, I believe this is the best choice from the standpoint of "DRY" (Don't Repeat Yourself).

wrote Dec 28, 2009 at 4:43 AM

wrote Feb 2, 2013 at 2:24 AM

wrote May 14, 2013 at 9:16 PM