Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Yes, you may create an <code>app/views/shared/_flash_messages.js.rjs</code> partial, which you can then render from anywhere (e.g. from other <code>rjs</code> partials.)</p> <p>My approach in these kinds of applications has been as follows:</p> <ul> <li><p>for non-AJAX responses that may have a flash:</p> <ul> <li>in the layout (e.g. <code>layouts/application.erb</code>), add e.g.:<br/><code>render :partial =&gt; 'shared/flash_messages.html.erb'</code></li> </ul></li> <li><p>for AJAX responses that may also need to display a flash message, I added the following <code>rjs</code> code:</p> <ul> <li>in each <code>rjs</code> response (e.g. <code>controller/action.js.rjs</code>), add e.g.:<br/><code>render :partial =&gt; 'shared/flash_messages.js.rjs'</code></li> </ul></li> </ul> <p>Where the two partials do the necessary to render the flash, then call <code>flash.discard(:error)</code> or <code>flash.discard(:notice)</code> as appropriate.</p> <p>Sample <code>app/views/shared/flash_messages.html.erb</code> file:</p> <pre><code>&lt;% if flash[:error] %&gt; &lt;div id="flash_message" class="error"&gt;&lt;%= h(flash[:error]) %&gt;&lt;/div&gt; &lt;% flash.discard(:error) %&gt; &lt;% elsif flash[:notice] %&gt; &lt;div id="flash_message" class="notice"&gt;&lt;%= h(flash[:notice]) %&gt;&lt;/div&gt; &lt;% flash.discard(:notice) %&gt; &lt;% else %&gt; &lt;div id="flash_message" style="display: none;" /&gt; &lt;% end %&gt; </code></pre> <p>Sample <code>app/views/shared/flash_messages.html.rjs</code> file:</p> <pre><code>if !flash[:error].blank? page['flash_message']. replace_html(flash[:error]). removeClassName('notice'). addClassName('error'). show() else page['flash_message']. replace_html(flash[:notice]). removeClassName('error'). addClassName('notice'). show() end </code></pre>
    singulars
    1. This table or related slice is empty.
    1. PODRY up js.erb files (include another js.erb file)
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USTim Cooper
    1. USvladr
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODRY up js.erb files (include another js.erb file)
      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. VTAcceptedByOriginator
    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. COThankyou. This was exactly the kind of example I was hoping for. My js.erb files is much cleaner now ;)
      singulars
      1. PO
      1. USatmorell
 

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