<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Indeed<br>
    </div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix">On 19/09/2019 17:56, DelazJ wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAECJsSrjGKX97iR8fCF2r=tcJYD6Z+3dm-JKWYB4cteBN-Cz+A@mail.gmail.com">
      <div dir="ltr">You mean, it's the selected field in the primary
        key drop-down menu in DB manager when you want to add the layer?<br>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">Le jeu. 19 sept. 2019 à 16:42,
          Janneke van Dijk <<a href="mailto:janneke.qgis@gmail.com"
            moz-do-not-send="true">janneke.qgis@gmail.com</a>> a
          écrit :<br>
        </div>
        <blockquote class="gmail_quote">
          <div>
            <div class="gmail-m_-3248680282170132592moz-cite-prefix">Hi
              Harrissou,</div>
            <div class="gmail-m_-3248680282170132592moz-cite-prefix">Thanks
              for the quick response - indeed, I indicated the assetid
              which is a unique value. That did not solve the problem,
              alas...</div>
            <div class="gmail-m_-3248680282170132592moz-cite-prefix">Janneke<br>
            </div>
            <div class="gmail-m_-3248680282170132592moz-cite-prefix"><br>
            </div>
            <div class="gmail-m_-3248680282170132592moz-cite-prefix">On
              19/09/2019 17:31, DelazJ wrote:<br>
            </div>
            <blockquote type="cite">
              <div dir="ltr">
                <div>Hi Janneke,</div>
                <div><br>
                </div>
                <div>Maybe you need a field that would uniquely identify
                  the 170 asset rows (their primary key). You can use an
                  ID field of your asset layer or construct one with
                  row_number function?</div>
                <div><br>
                </div>
                <div><br>
                </div>
                <div>Regards,</div>
                <div>Harrissou<br>
                </div>
              </div>
              <br>
              <div class="gmail_quote">
                <div dir="ltr" class="gmail_attr">Le jeu. 19 sept. 2019
                  à 16:10, Janneke van Dijk <<a
                    href="mailto:janneke.qgis@gmail.com" target="_blank"
                    moz-do-not-send="true">janneke.qgis@gmail.com</a>>
                  a écrit :<br>
                </div>
                <blockquote class="gmail_quote">Dear list,<br>
                  <br>
                  I have a parent - child relationship set up between a
                  table location (1, <br>
                  the parent) and a table assets (many, the child). The
                  location table <br>
                  contains geometry, the asset table does not. I would
                  like to be able to <br>
                  display each record in the asset table with the
                  corresponding geometry <br>
                  of the location table - so if there are 3 assets at a
                  certain location, <br>
                  I would like to display 3 points (each with identical
                  geometry).<br>
                  <br>
                  What I can do with the DB manager is:<br>
                  <br>
                  select location_point.geom, asset_point.assetid,
                  location_point.fid  <br>
                  from asset_point cross join location_point on
                  asset_point.locationid = <br>
                  location_point.fid<br>
                  <br>
                  this query yields 170 records, corresponding with the
                  number of records <br>
                  in the assets table. When I load as a new layer, the
                  result is a table <br>
                  with 170 records, but 100 filtered (the total number
                  of locations). I <br>
                  chose assetid to be the unique id (which it is).<br>
                  <br>
                  Is that expected behaviour? How else can I display all
                  the records in <br>
                  the assets table (instead of only the 100 that are
                  filtered now)? I know <br>
                  I can do it in Postgres but for my purpose now I don't
                  want to go there.<br>
                  <br>
                  Any insights deeply appreciated!<br>
                  <br>
                  Janneke<br>
                  <br>
                  <br>
                  _______________________________________________<br>
                  Qgis-user mailing list<br>
                  <a href="mailto:Qgis-user@lists.osgeo.org"
                    target="_blank" moz-do-not-send="true">Qgis-user@lists.osgeo.org</a><br>
                  List info: <a
                    href="https://lists.osgeo.org/mailman/listinfo/qgis-user"
                    rel="noreferrer" target="_blank"
                    moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/qgis-user</a><br>
                  Unsubscribe: <a
                    href="https://lists.osgeo.org/mailman/listinfo/qgis-user"
                    rel="noreferrer" target="_blank"
                    moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/qgis-user</a></blockquote>
              </div>
            </blockquote>
            <p><br>
            </p>
          </div>
        </blockquote>
      </div>
    </blockquote>
    <p><br>
    </p>
  </body>
</html>