Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Yes, <code>jQuery.noConflict</code> is a good start, but since the "other library" you are using is also jQuery, there will probably be complications. </p> <p>When you load jQuery, it defines <code>$</code> and <code>jQuery</code> as global variables. Using <code>.noConflict</code> will "relinquish control of the <code>$</code> variable" - meaning whatever <code>$</code> was before, it will be set to again. If v1.3.2 is loaded first and you load latest pack (1.6.4 as of right now) next, <code>.noConflict</code> will make <code>$</code> refer to v1.3.2 but <code>jQuery</code> will still refer to 1.6.4.</p> <p>Basically, you need to alias jQuery before you load the latest pack. <a href="http://jsfiddle.net/RHMWH/1/">See my fiddle used to simulate your situation</a> (also pasted below).</p> <pre><code>&lt;script type="text/javascript"&gt; //alias v.1.3.2 var $132 = $; &lt;/script&gt; &lt;script type="text/javascript" src="http://code.jquery.com/jquery-latest.pack.js"&gt;&lt;/script&gt; &lt;script type="text/javascript"&gt; //alias v1.6.4 var $164 = $, jQuery164 = $; //reset original variables to v1.3.2 $ = jQuery = $132; console.log("v1.3.2: ", $().jquery, jQuery().jquery) console.log("v1.6.4: ", $164().jquery, jQuery164().jquery) $('div') //selected using v1.3.2 $164('div') //selected using v1.6.4 &lt;/script&gt; </code></pre> <p>After loading 1.6.4, you need to alias it and set <code>$</code> and <code>jQuery</code> back to the 1.3.2 objects. This doesnt use <code>.noConflict</code> becuase it essentially does the same thing. RichFaces will continue to work using 1.3.2 and you will write your code against the aliased 1.6.4 version. In my fiddle, that means using <code>$164</code> instead of using <code>$</code>. I hope that makes sense. I am sure the fiddle will be clearer.</p> <hr> <p>Finally, it is fine to develop code using <code>jquery-latest.pack.js</code> but you shouldn't ever use that on your production website. The reason is because at some point in the future, jQuery will be updated. If you are loading the latest pack, those updates may break the functionality of your site without you even knowing it. It's safer to just pick a version and stick to it, only upgrading only when you confirmed that your site will continue to function properly.</p>
    singulars
    1. This table or related slice is empty.
    1. POChange the JQuery version used in richfaces
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USJeff
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POChange the JQuery version used in richfaces
      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. VTUpMod
    1. COI understand the answer but I can't implement the solution. There is a conflict with Richfaces (extendeddatatables can't be displayed)
      singulars
      1. PO
      1. USJean-Charles
    2. COThat sounds like it is a different problem than you originally mentioned - or at least I dont see the connection. How are you including RichFaces and jQuery?
      singulars
      1. PO
      1. USJeff
    3. COMy project is using JSF1.2/Richfaces (with maven). When I test to include another version of jQuery, I add `<script type="text/javascript"` in the header...
      singulars
      1. PO
      1. USJean-Charles
 

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