Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>One of the problems I see is that the Name fields is editable. If the field is changed, all the overlapping has to be recalculated. Not only is that is a performance issue, it is also a usability problem: what if one wants to change a name and the script, seeing discrepancies, forbids it?</p> <p>A solution would be to change the table to one resembling the diagram below:</p> <pre><code>[ Add Employee ] | Name | Start | End | Wages | ========================================== | | 0 | 50 | 100 | | Brian | 50 | 70 | 150 | | | 100 | 150 | 200 | | [ Add Rule ] | ------------------------------------------ | Another | 0 | ... | etc | </code></pre> <p>The [ Add Employee ] button would ask for a name and add a cell in the first column, and a line in the next three: with a default Start value of 0. The user can then enter data on the next fields, and can [ Add Rules ] as wanted. A good restriction could be to lock the values of the Start column and set them to the End value of the previous line.</p> <pre><code>$('#Brian .LineN input.start').val( $('#Brian .LineN').prev().find('input.end').val() ); </code></pre> <p>Then adding a comparison function to check if the End value is lower than the Start value is trivial to implement.</p> <p>Deleting a rule could simply follow the same procedure as for adding a line: the line below the one deleted (if any) would set its Start value as the now previous line's End.</p> <p>The real difficulty would be to insert lines at arbitrary points. I'm not going to think about that one, though.</p> <p>EDIT: If a rewrite is out of the question, then just disabling the start should be enough. However, IMHO I would rather (re)write something with no caveats than spend time later on numerous bugs and feature requests.</p>
    singulars
    1. This table or related slice is empty.
    1. POJQuery: Validating Data Rules
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USFélix Saparelli
    1. USFélix Saparelli
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POJQuery: Validating Data Rules
      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
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTBountyClose
    1. COThis is definitely a better solution, how would you suggest I process the input fields? right now I have to use to different input names Right now I use `<td><input type='text'name='Default_wage[]'></td>` for Default and `<td><input type='text'name='wage[]'></td> ` for everyone else. The $_POST is parsed by PHP on submitting. I guess one way would be allowing looping through all the post vars. Is it possible to use Associative Arrays in the name? for example `<td><input type='text'name='wage["Default"]'></td>`
      singulars
      1. PO
      1. USParoX
    2. COYou can use associative arrays in POST. It would also be relatively easy to use jQuery to generate names for the input fields depending on where they are. But... if you use jQuery, why not use XHR? You could use JSON to pass on whatever structure you decide on.
      singulars
      1. PO
      1. USFélix Saparelli
    3. COOK. Thats good to know but totally re-writing what I already have is a last thing I want right now.
      singulars
      1. PO
      1. USParoX
 

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