Hey Darius, Below are the list of anomalies detected by schema spy. *Things that might not be 'quite right' about your schema:*
- *Columns whose name and type imply a relationship to another table's primary key:* Child Column Implied Parent Columnactive_list<tables/active_list.html> .active_list_id active_list_problem <tables/active_list_problem.html> .active_list_id active_list_allergy <tables/active_list_allergy.html> .active_list_id active_list_problem <tables/active_list_problem.html> .active_list_id concept_set <tables/concept_set.html>.concept_id concept_numeric <tables/concept_numeric.html>.concept_id concept_set_derived <tables/concept_set_derived.html>.concept_id concept_numeric <tables/concept_numeric.html>.concept_id htmlformentry_html_form <tables/htmlformentry_html_form.html>.id liquibasechangeloglock <tables/liquibasechangeloglock.html>.ID logic_rule_definition <tables/logic_rule_definition.html>.id liquibasechangeloglock <tables/liquibasechangeloglock.html>.ID orders<tables/orders.html> .concept_id concept_numeric <tables/concept_numeric.html>.concept_id patient_identifier <tables/patient_identifier.html>.patient_id patient<tables/patient.html> .patient_id 8 instances of anomaly detected - *Tables without indexes:* Anomaly not detected - *Columns that are flagged as both 'nullable' and 'must be unique':* Column cohort <tables/cohort.html>.uuidconcept <tables/concept.html>.uuid concept_answer <tables/concept_answer.html>.uuid concept_class<tables/concept_class.html> .uuid concept_datatype <tables/concept_datatype.html>.uuid concept_description <tables/concept_description.html>.uuid concept_name<tables/concept_name.html> .uuid concept_name_tag <tables/concept_name_tag.html>.uuid concept_proposal <tables/concept_proposal.html>.uuid concept_reference_source <tables/concept_reference_source.html>.hl7_code concept_set <tables/concept_set.html>.uuid concept_state_conversion<tables/concept_state_conversion.html> .concept_id concept_state_conversion<tables/concept_state_conversion.html> .program_workflow_id concept_state_conversion<tables/concept_state_conversion.html> .uuid drug <tables/drug.html>.uuid encounter <tables/encounter.html>.uuid encounter_type <tables/encounter_type.html>.uuid field<tables/field.html> .uuid field_answer <tables/field_answer.html>.uuid field_type<tables/field_type.html> .uuid form <tables/form.html>.uuid form_field <tables/form_field.html> .uuid global_property <tables/global_property.html>.uuid hl7_in_archive<tables/hl7_in_archive.html> .uuid hl7_in_error <tables/hl7_in_error.html>.uuid hl7_in_queue<tables/hl7_in_queue.html> .uuid hl7_source <tables/hl7_source.html>.uuid location<tables/location.html> .uuid location_tag <tables/location_tag.html>.uuid metadatasharing_subscription <tables/metadatasharing_subscription.html> .group_uuid note <tables/note.html>.uuidnotification_alert<tables/notification_alert.html> .uuid notification_template <tables/notification_template.html>.uuid obs<tables/obs.html> .uuid order_type <tables/order_type.html>.uuid orders<tables/orders.html> .uuidpatient_identifier <tables/patient_identifier.html>.uuid patient_identifier_type <tables/patient_identifier_type.html>.uuid patient_program <tables/patient_program.html>.uuid patient_state<tables/patient_state.html> .uuid person <tables/person.html>.uuid person_address<tables/person_address.html> .uuid person_attribute <tables/person_attribute.html>.uuid person_attribute_type <tables/person_attribute_type.html>.uuid person_name <tables/person_name.html>.uuid privilege<tables/privilege.html> .uuid program <tables/program.html>.uuid program_workflow<tables/program_workflow.html> .uuid program_workflow_state <tables/program_workflow_state.html>.uuid relationship <tables/relationship.html>.uuid relationship_type<tables/relationship_type.html> .uuid report_object <tables/report_object.html>.uuid report_schema_xml<tables/report_schema_xml.html> .uuid role <tables/role.html>.uuid serialized_object<tables/serialized_object.html> .uuid 55 instances of anomaly detected - *Tables that contain a single column:* Anomaly not detected - *Tables with incrementing column names, potentially indicating denormalization:* Table location <tables/location.html>person_address<tables/person_address.html> person_name <tables/person_name.html> 3 instances of anomaly detected - *Columns whose default value is the word 'NULL' or 'null', but the SQL NULL value may have been intended:* Anomaly not detected On Thu, Jan 19, 2012 at 7:27 PM, Darius Jazayeri <[email protected]>wrote: > Hi Kishore, > > Sounds cool. Can you give a couple examples of the sorts of anomalies? > > -Darius (by phone) > On Jan 19, 2012 4:26 AM, "Harsha Siriwardena" <[email protected]> > wrote: > >> thx bro! >> >> On Thu, Jan 19, 2012 at 2:31 PM, Yekkanti Kishore Kumar < >> [email protected]> wrote: >> >>> Hi, >>> I've always didn't understood the complete (db)schema structure of >>> OpenMRS. Schema Spy <http://schemaspy.sourceforge.net/> helped me in >>> understand the db schema better. >>> It also gave a list of anomalies in the database which we might need to >>> consider. Starting up with Schema Spy is very easy. Just download the jar, >>> point it to your database and thats it. >>> >>> I'm unable to attach the report generated as it is more than 25Mb (close >>> to 30MB). >>> *Command I used: * *java -jar schemaSpy_5.0.0.jar -t mysql -host >>> localhost -dp ~/Desktop/mysql-connector-java-5.1.7-bin.jar -db openmrs -u >>> root -p password -o ~/Desktop* >>> >>> -- >>> Regards, >>> Kishore Kumar Yekkanti. >>> ------------------------------ >>> Click here to >>> unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from >>> OpenMRS Developers' mailing list >> >> >> ------------------------------ >> Click here to >> unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from >> OpenMRS Developers' mailing list > > ------------------------------ > Click here to > unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from > OpenMRS Developers' mailing list > -- Regards, Kishore Kumar Yekkanti. _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
