Hot answers tagged

4

The names of your tables should be BUSINESSES, TREATMENTS, CLIENTS, EMPLOYEES, APPOINTMENTS. Nobody appends "_TABLE" to their table names, just as nobody appends "_Word_Document" to their word document names. Also, we usually do not include joined fields in table designs. The fact that these fields are available is evident by the presence of the foreign ...


3

You could have a separate table for works in progress. You would use more or less the same table scheme, just with each field set as nullable. When a record is initially created, it goes into the incomplete records table (you could have a check to put first time completed records directly into your completed records table, of course). Once a record has ...


2

One possibility, not yet mentioned, is that you don't stick an incomplete record in the database at all - you just hold it as a blob (serialized by some means) somewhere (could be in the database, could be elsewhere). It rather depends on what, if anything, is done with incomplete records (this is about workflow and related). Specifically if 90% of the code ...


2

You shouldn't split a normalized table just because it have "many" fields. It will not make anything easier.


2

You should consider the idea that specifications change. Today there are 50 default fields, tomorrow there could be 51. You do not want to be adding a column every time the requirements change. The reverse might also be true; what if a column is no longer mandatory or is no longer required? The sample ERD below allows the following: people can take a ...


2

But another problem comes with the restful api. I'm not sure what is a good way to expose this kind of data. Any way you like. REST doesn't care, so long as the application state is completely captured in the hypermedia. In particular, REST doesn't care how you spell your URI. Convention is to express hierarchy in the path, and filtering in the ...


1

Every book can have several users as authors and at the same time every user can be an authors of several books. So you have an n:m relationship. No problem, that justmeans you'll need a link table that references both entities. they can also keep this association private Even less of a problem: you add visibility as another attribute to the ...



Only top voted, non community-wiki answers of a minimum length are eligible