One-to-one communications and normalization of the database

[Marcee]

The predicate area is: there are users and doctoral tickets they can take. The connection between them is one or more. The order must be confirmed by the user in some way. Talon can have one status at every time - "free," "proclaimed, but not confirmed by a laser," "crazed and confirmed by a laser."

There are two tables on this mm: UsersUsersand ticketsTicket

But the fields marked green in the table. Ticket (sighs)Status♪ UserId♪ VerificationCode and OrderDate() Not directly related to the plate is the attribution of the order. All of them, apart from their status, have empty meanings (NULLIf the car is still occupied.

The question is whether the data structure is good now, or is it wrong, and this situation requires another? It would be interesting to know which of the normal forms corresponded to the current structure; whether there were irregularities in its normal forms and, if so, how to correct them.

It was an idea to put these attributes in a separate table (e.g. "Prosecutions") and tie it to the plates. TicketOne-to-one. But in this case, I get the extra difficulty in working with the plates and the orders from the application. I'd love to hear any advice, thank you.

[jules]

To speak of normalization, natural keys and dependence must be determined. You only see the ID.

Does it make sense to an unsuitable plate? Records?

With regard to the " unnecessary difficulty in dealing with the plates and orders from the annex " , re-establishing the presentation of the scheme could be created.