If I call removeConceptName on a concept and then try to save the concept, I get a foreign key constraint violation on ConceptWord.
I shouldn't have to do this to save a concept:
c = Context.getConceptService().saveConcept(c);
The fix for this is to clean up the conceptindex/conceptword in the ConceptServiceImpl.saveConcept method before saving the concept via the dao. (currently its immediately after)
Add a unit test to prove that this was failing and is now working.