Alter schema and table names to improve 'self documentation' properties

Suggest changing default schema name from 'fakedata2' to 'snofyre'

Some schema table names carry prefixes to indicate broad purpose e.g. epr_, but 
this currently isn't carried through. It could help understanding of the 
backend if it was.

E.g. patient_table -> ehr_master_patient_index
     clinical_entry -> ehr_clincal_entry
     clinical_entity -> ehr_clinical_entity

A naming prefix for those tables that hold the expression repository would be 
useful.

E.g. exp_expression, exp_expression_tc_table, exp_close_to_user_expressions, 
exp_unique_expressions_table

A lot of tables don't appear to be used at all. If they really are legacy of 
earlier stages in the software development, it would help to have a spring 
clean. 

E.g. person_table, parents

Original issue reported on code.google.com by jeremy.r...@googlemail.com on 19 Jan 2011 at 11:00

yonite / snofyre

Alter schema and table names to improve 'self documentation' properties #20