Good practices in data modeling

2

I'm an intern and I'm developing a small application to help the quality and development staff to register the use cases and etc, the application is very simple even, it is done in Angles with backend C #, however we arrived in a point of the application where it is necessary to validate these use cases, I as an intern suggested the following bank:

However,whenhegavemetheAPI,heputthetablestogether.

AsatraineeandIhaveasmallknowledge,butstill,Istillthinkthatjoiningbothtablesinoneisnotagoodpractice,IwouldlikethecommunitytoknowifthatwayIaddmyknowledgeinBD

Thanksinadvance,

Edit1:Sorryforthelackofinformation,Itriedtobeabitbrieftosaveyourtime.

IhaveaSTARTscreenforvalidatingausecase(Below)

ImodeledthetablethatwaybecauseIneedtostorethebeginningandendoftheUCvalidationround,iftheuserexitsbeforefinishingvalidating,hecancontinue,soIcreatedthosetables,soIwouldhaveasimplerelationshiptowork,andsimplerAPIrequests,butthetablethatwasdeliveredtomewas

Instead of two tables, only one table with auto referencing.

Not that this is a big problem, I worry more about bank maintenance and etc., although it is a small system with just over 2000 thousand records.

    
asked by anonymous 15.05.2017 / 20:20

0 answers