Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>i see that not all your tables have a PK, actually i only see that the user table has one, and the storyboard is using the name and owner as PK?</p> <p>i prefer to use an id to all my tables, except the intermediary tables used for NxN relation, like you did on the authors and reviewers. You did the same but you called it GID. I'd use them as PK (and auto incremental also). </p> <p>Don't worry if an object has the same GID as another object on a different table, because in your comments table you have an <code>ObjType</code> that specifies the table related to the object. So it will be ok if a User's GID is the same as the StoryBoard's GID.</p> <p>I'm not used to the sql-server diagrams, but it seems that the relations are not well defined: i see that user and storyboard are related in a 1xN but it looks like the storyboard and the slides are related in a 1x1 relation, when it should also be a 1xN</p> <p>A storyboard has a owner and different authors, that means that if i create a storyboard, the storyboard will have my id in the OwnersUserId and my id will also be stored in the authors table? if yes, it seems unnecessary. Or.. well.. it depends on the conception of your model. I see two options:</p> <ul> <li><p>a StoryBoard has ONE author and ONE OR MANY collaborators </p> <p>(dont change your model, only rename the authors table to collaborators or something more precise)</p></li> <li><p>a StoryBoard has ONE OR MORE authors and one of them is the owner</p> <p>(remove the 1xN relation between Users and storyboard and add a <code>type</code> columm to the Authors table)</p></li> </ul> <p>A final observation:</p> <blockquote> <p>User should be able to view and load only the storyboards created by him.</p> </blockquote> <p>it wont change the data model.. =) but, if only the authors can view the storyboards, then who will review them?</p> <p>My observations are just superficial, I find the model well adjusted to the problem</p> <p>Good Luck</p>
    singulars
    1. This table or related slice is empty.
    1. POSuggest improvements for the database design
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USpleasedontbelong
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POSuggest improvements for the database design
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COthanks for you valuable input, yeah i think i will remove the GID and replace with a normal PK(auto incremental) .
      singulars
      1. PO
      1. USdeovrat singh
    2. COstoryboard and slide is a 1 X N relation as one storyboard can have many slides, for this StoryBoardGID in slide is the foreign key and corresponding StoryBoardGID in StoryBoard is the primary key. In this case, for a storyboard there is one or more author which can edit the content of storyboard,one owner(is also an author) who has created the storyboard,zero or more reviewers which only have the right to comment on different entities.Authors can also comment on entities.
      singulars
      1. PO
      1. USdeovrat singh
    3. COAlso one concern for me is that I want to ensure that one owner cannot have more than one storyboard with the same name, for which I was adding (name,ownerid) as primary key , but if I remove the owner id from the storyboard table and add a type in author then how should I ensure that a owner cannot have two same named storyboards. I forgot to mention about reviewer in the loading storyboard part.Thanks for pointing that out
      singulars
      1. PO
      1. USdeovrat singh
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload