Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>First Suggestion:</strong></p> <p>Create a Javascript Variable that will reference the button clicked. Lets call it <em>buttonIndex</em></p> <pre><code>&lt;input type="submit" onclick="buttonIndex=0;" name="save" value="Save" /&gt; &lt;input type="submit" onclick="buttonIndex=1;" name="saveAndAdd" value="Save and add another" /&gt; </code></pre> <p>Now, you can access that value. 0 means the save button was clicked, 1 means the saveAndAdd Button was clicked.</p> <p><strong>Second Suggestion</strong></p> <p>The way I would handle this is to create two JS functions that handle each of the two buttons.</p> <p>First, make sure your form has a valid ID. For this example, I'll say the ID is "myForm"</p> <p><strong>change</strong></p> <pre><code>&lt;input type="submit" name="save" value="Save" /&gt; &lt;input type="submit" name="saveAndAdd" value="Save and add another" /&gt; </code></pre> <p><strong>to</strong></p> <pre><code>&lt;input type="submit" onclick="submitFunc();return(false);" name="save" value="Save" /&gt; &lt;input type="submit" onclick="submitAndAddFunc();return(false);" name="saveAndAdd" value="Save and add </code></pre> <p>the return(false) will prevent your form submission from actually processing, and call your custom functions, where you can submit the form later on.</p> <p><strong>Then your functions will work something like this...</strong></p> <pre><code>function submitFunc(){ // Do some asyncrhnous stuff, that will later on submit the form if (okToSubmit) { document.getElementById('myForm').submit(); } } function submitAndAddFunc(){ // Do some asyncrhnous stuff, that will later on submit the form if (okToSubmit) { document.getElementById('myForm').submit(); } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POForm onSubmit determine which submit button was pressed
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDutchie432
    1. USDutchie432
    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
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COSort-of. I would have to then add hidden fields in each one of the submit functions, one with name="save" value="..." and etc. and I'm trying to avoid that. Don't get me wrong it's a valid solution. I'm just looking for something more elegant.
      singulars
      1. PO
      1. USMcTrafik
    2. COHidden Fields? For what?
      singulars
      1. PO
      1. USDutchie432
    3. CO#2 won't work - when you used DOM-based event handlers, nothing will be executed after a `return` statement. So your calls to `submitFunc()` and `submitAndAddFunc()` will never fire.
      singulars
      1. PO
      1. USPeter Bailey
 

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