Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>EDITED:</strong><br> It seems that when using a multipage template approach (single html with all pages included) then <code>pageinit</code> is fired once since the pages are loaded in DOM and remain there when transitioning between pages.</p> <p>However when using multiple pages and navigating though Ajax you will notice that the pages contain an attribute <code>data-external-page="true"</code> except the first page. The first page is always cached in DOM even if you're using domCache false. But the pages except the first page are loaded and cleaned out after you leave them. That's why <code>pageinit</code> is fired on back/forward button clicks.</p> <p>The <em>domCache</em> sets whether to keep the page in the DOM after the user has navigated away from it. You can read about it on <a href="http://api.jquerymobile.com/page/" rel="nofollow">jQM docs</a>. By default the <em>domCache</em> option's value is <em>false</em>.</p> <p>Adding:</p> <pre><code>$(document).on('mobileinit', function () { $.mobile.page.prototype.options.domCache = true; }); </code></pre> <p>between jQuery js and jQuery Mobile js will cause the pages to be cache in DOM. Therefore pageinit will not fire.</p> <p>An alternative is to add <code>data-dom-cache="true"</code> on your anchor.</p> <p>The <strong>drawback</strong> of using domCache is that the DOM can be large, resulting in <strong>memory issues</strong>. In a such approach the DOM management is left on the developer.</p> <p>At last make sure that you're using the same jQ, jQM versions in your pages. The first 2 pages are using jQ 1.9.1, jQm 1.3.1 and the third page is using jQ 1.7.1, jQM 1.1.0. This is irrelevant with the specific issue but it worth to mention it.</p> <p>I hope this helps.</p>
    singulars
    1. This table or related slice is empty.
    1. POJQuery Mobile - Back and forward browser buttons fire the pageinit event
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USTolis Emmanouilidis
    1. USTolis Emmanouilidis
    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
    1. COThanks. is there any drawback in setting the domCache option to true. Would like to know why the default status is false. And, i was doing the following things in pageinit: 1. Loading the page data using ajax. 2. Registering the events for the page. So, if i make domcache as true, then pageinit will not be called on navigation. And, the data will not change at all. Should i move the loading of data to pageshow then. The problem then will be pageshow will load data again even on back button press. It has become even more confusing now.
      singulars
      1. PO
      1. USuser694688
    2. COLooking for more clarification on the above answer.
      singulars
      1. PO
      1. USuser694688
    3. COPageshow will be fired even if domCache is true. I would not use the global domCache option but the corresponding anchor attribute.The drawback is that the DOM can be large, resulting in memory issues. That's why JQM has disabled this option by default.
      singulars
      1. PO
      1. USTolis Emmanouilidis
 

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