A web application developed as my final project for the Computer Engineering Degree. It allows users to model entity-relationship diagrams and export them to SQL scripts after validation.
There should be a mechanism to control and eliminate duplicate names among attributes, entities, and relationships within the diagram to ensure data integrity and prevent conflicts.
Goal:
Implement a feature that prevents the diagram to have repeated numbers at initialization. The user can still set repeated names but that will result in a validation error.
Proposed Solution:
Check for duplicate attribute names within each entity.
Check for duplicate entity and relation names.
Note
When I say that the user can set repeated names and that will result in a validation error I'm referring to #12
Background:
There should be a mechanism to control and eliminate duplicate names among attributes, entities, and relationships within the diagram to ensure data integrity and prevent conflicts.
Goal:
Implement a feature that prevents the diagram to have repeated numbers at initialization. The user can still set repeated names but that will result in a validation error.
Proposed Solution:
Check for duplicate attribute names within each entity. Check for duplicate entity and relation names.
Note
When I say that the user can set repeated names and that will result in a validation error I'm referring to #12