Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>From the <a href="http://download.oracle.com/javaee/5/tutorial/doc/bnbuf.html" rel="nofollow">Java EE tutorial</a> I read the following:</p> <blockquote> <p><strong>Return Types</strong></p> <p>The return type of the SELECT clause is defined by the result types of the select expressions contained within it. If multiple expressions are used, the result of the query is an Object[], and the elements in the array correspond to the order of the expressions in the SELECT clause, and in type to the result types of each expression.</p> </blockquote> <p>Now your query looks like:</p> <pre><code>SELECT g.filename, g.description, g.uploadDate FROM Garbage g; </code></pre> <p>From your entity class <code>Garbage</code> I read that <code>filename</code>, <code>description</code>, <code>uploadDate</code> are Strings. Then your query returns a list of <code>Object[]</code> and each array element contains a String and not a <code>Garbage</code> object.</p> <p>If your array contains Strings and not Garbage, you cannot call <code>garbage[0].filename</code> in your facelet.</p> <p>Try to change your Query in the following way:</p> <pre><code>SELECT g FROM Garbage g; </code></pre> <p>Then you get a <code>List&lt;Garbage&gt;</code>. In the <code>SearchEJB</code> change the method signature to the following:</p> <pre><code>public List&lt;Garbage&gt; findAllGarbage() </code></pre> <p>Change the methods in your <code>ResultsController</code> managed bean accordingly (now you always need a <code>List&lt;Garbage&gt;</code> and not a <code>List&lt;Garbage[]&gt;</code>).</p> <p>Finally modify your <code>p:dataTable</code> (shown for the first column):</p> <pre><code>&lt;p:column sortBy="#{garbage.filename}"&gt; &lt;f:facet name="header"&gt; &lt;h:outputText value="Filename" /&gt; &lt;/f:facet&gt; &lt;h:outputText value="#{garbage.filename}" /&gt; &lt;/p:column&gt; </code></pre> <p><strong>UPDATE:</strong></p> <p>If you want to keep your query you could convert the <code>Object[]</code> into a list of <code>Garbage</code> objects and leave the missing fields empty. Something like this (add a constructor to your Garbage class):</p> <pre><code>List&lt;Garbage&gt; gList = new ArrayList(); for (Object[] o: query.getResultList()) { gList.add(new Garbage(o[0], o[1], o[2]); } </code></pre> <p><strong>UPDATE 2:</strong></p> <p>In your update you missed again, that your array contains strings. And the strings are ordered as your select expression is ordered: element 0: filename, element 1: description, element 2: uploadDate.</p> <p>Change your loop in the following way:</p> <pre><code>for (Object o: query.getResultList()) { Garbage tmpG = new Garbage(); tmpG.setFilename(o[0]); tmpG.setDescription(o[1]); tmpG.setUploadDate(o[2]); gList.add(tmpG); } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POdataTable sortBy function does not work(primefaces)
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMatt Handy
    1. USMatt Handy
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POdataTable sortBy function does not work(primefaces)
      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
    1. COThat is right but i cant just do that. I need to use the indexes, because is the only way i can avoid returning the byte[] that the garbage objects contain. If i change to just SELECT g FROM Garbage g; The performace will drop drastically because in each query it will be actually retrieving files for the byte[] type field. There has to be another way :(
      singulars
      1. PO
      1. USsfrj
    2. COThen you have to use the Object[] but I don't know if Primefaces sorting supports it. And `<p:column sortBy="#{garbage[0]}">` won't work?
      singulars
      1. PO
      1. USMatt Handy
    3. CONo doesnt work. Currently the column looks like this: <p:column sortBy="#{garbage[0]}" parser="string">... There is a bit of progress, now the console does not say SEVERE: Error in sorting. But still does not sort the column. Maybe i just need now to do some kind of casting at "#{garbage[0]}". But how?
      singulars
      1. PO
      1. USsfrj
 

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