database - is it a good way to use 1-1 relationship in this case? -


i have database table ticket containing:

[id, user_id, project_id, title, steps_to_reproduce_issue, expected_result, actual_result, additional_comments, ticket_attachment_id, status, priority, categories, date_created, date_modified] 

is way put following attributes [title, steps_to_reproduce_the_issue, expected result, actual_result, additional_comments] separate table ticketdescription, , use 1-1 relationship ticket-ticketdescription tables, , add ticket_description_id ticket ?

i hope understood case.

consider have 3 occasions of same show. (i.e. diffrent hours) - better reuse ticketdescription 3 occasions, right?

so in point of view it's better use 1 many relation instead of declaring every time description.

think distribution of fields.


Comments

Popular posts from this blog

Java 3D LWJGL collision -

spring - SubProtocolWebSocketHandler - No handlers -

methods - python can't use function in submodule -