Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Here's a possible solution, given in the form of an employees-to-projects m:m relationship. Each employee can work on many projects, each project can involve many employees.</p> <p>From left to right, you show the following:</p> <p>A panel showing the details of the currently selected employee.</p> <p>A list of all employees, where each item in the list shows the employee's name as a clickable link or button (to display details in the detail panel). At the head of the list is a toggle button which filters the projects list to only those associated with the currently selected employee. At the foot of the list is a button to add a new employee, which display an empty details panel ready to accept input.</p> <p>A vertical space in the middle with a single "Link" button allowing the user to link the currently selected employee with the currently selected project. Clicking this button would open a dialog allowing the user to enter details of the link (i.e. how long the employee is assigned, what role the eployee will play, etc).</p> <p>A list of all projects, where each item in the list shows the project's name as a clickable link or button (to display details in the detail panel). At the head of the list is a toggle button which filters the employees list to only those associated with the currently selected projet. At the foot of the list is a button to add a new project, which display an empty details panel ready to accept input.</p> <p>A panel showing the details of the currently selected project.</p> <p>Obviously, you'd have to limit the size of the details panels, maybe by only showing the details relevant to the m:m relationship. You might even add a button on the details panel to open a more detailed pop-up window, or you might do away with the details panel altogether, if you're mainly interested in managing the links. This UI would work really well on wide-aspect screens.</p> <p>HTH! Klay</p>
    singulars
    1. This table or related slice is empty.
    1. POGUI patterns to edit data with many-to-many relationship
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USKlay
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COKlay - OK, i think I'm being dense, how is this different from original poster's own solution?
      singulars
      1. PO
      1. USDVK
    2. COI'm honestly not sure what to make of the OP's solution. It may be that the "Add table3 item" box was supposed to be an "Add table2 item" box, which would make it more understandable.
      singulars
      1. PO
      1. USKlay
    3. COSince I don't understand how the OP' solution was supposed to work, I don't understand exactly how the difficulties arise. What does it means to "add" table3 items to table1 items (or vice versa)? You're simply making associations between the two. Since associations (as opposed to parent-child relationships) are symmetrical, Disadvantage 1 is moot.
      singulars
      1. PO
      1. USKlay
 

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