Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>NOTE:</strong> I'm guessing you know why adding a panel fixes the problem, but I'm including additional detail for the benefit of others who might encounter the same behavior.</p> <p>Almost everything in XPages is processed hierarchically. So variables, data sources, and component references are often only valid within the context of a container.</p> <p>Given the source code you listed in your question, the data source is attached to the "view root", so it's valid anywhere on that page (or Custom Control). As the page is evaluated at runtime, the root component will be processed first, and part of that evaluation is determining whether the data source attached to it needs to be created or already exists, based on its scope.</p> <p>Once that's finished, it can start processing any child components, which -- again, in your example -- includes the <code>jdbcConnectionManager</code>.</p> <p>This is why, as Panu mentioned, the data source can't refer to the component: it's attached to a parent.</p> <p>But data sources can be associated with specific panels, not just view roots. If you add a <code>panel</code> as a sibling to the <code>jdbcConnectionManager</code> -- specifically, <em>below</em> it -- and move the data source to that <code>panel</code>, here's what then happens at runtime:</p> <ul> <li>Domino starts processing the view root; not much to do here now, so it just hands off control to its children.</li> <li>The first child is the <code>jdbcConnectionManager</code>, so whatever encoding needs to happen for that component occurs before dealing with the rest.</li> <li>Next, the panel is evaluated. This includes evaluating the data source, which can now refer to the connection manager component, since it has already been loaded.</li> <li>Finally, all of the panel's descendant components (its children, their children, and so on) are evaluated. So anything that needs to refer to the data source does need to be defined somewhere inside this panel, but the data source can refer to the connection manager without blowing up specifically because that component <em>isn't</em> inside the panel... it's already been processed by the time the panel is dealt with.</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POCan JDBCConnectionManager be used with JDBCRowSet?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USTim Tripcony
    1. USTim Tripcony
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POCan JDBCConnectionManager be used with JDBCRowSet?
      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. COThe `jdbcRowSet` is the datasource so did you mean `jdbcConnectionManager`?
      singulars
      1. PO
      1. USPanu Haaramo
    2. CODoh! Yes, good catch. I've edited the answer accordingly.
      singulars
      1. PO
      1. USTim Tripcony
    3. COA very clear explanation, thanks. However, i am puzzled as to why the setup works with a `jdbcQuery` datasource. There must be some difference in their initialization procedures (lazy vs. direct style).
      singulars
      1. PO
      1. USLauri Laanti
 

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