heres my quick comments on your DB ideas:
aa_character:
the two min_* fields should not be there, as they are not character specific.
Further, they are already be specified in altadv_vars.
the remaining fields from aa_character would belong in the character table,
but there are more fields from the player profile which would be needed to make
their removal from the blob complete... and it should really be an all or nothing thing.
aa_info:
table should be normalized:
(character_id, aa_skill_id)
and thats it.
aa_data:
this table is a mess, it contains components from several different concepts:
Its only purpose should be to tell eqemu what to do with this AA.
this is what aa_actions is for, so what your really proposing is a mod to aa_actions.
the key should be aa_skill_id (aa_actions was aaid,rank but needs changing too since soe changed it)
aa_name, aa_class,aa_cost,aa_type,level, restriction... are already in altadv_vars
im not sure I see the usefuless of the other fields which are not in aa_actions either.
|