Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You need another join to the same table to pull back all the records with an MMSI that is in the result of your existing query. Something like this should do it:</p> <pre><code>; WITH positions AS ( SELECT MMSI , Message_ID , "Time" , Latitude , Longitude FROM dbo.DecodedCSVMessages_Staging WHERE Message_ID IN (1, 3) AND Latitude &gt; 55 AND Latitude &lt; 85 AND Longitude &gt; 50 AND Longitude &lt; 141 ) , all_positions AS ( SELECT MMSI , Message_ID , "Time" , Latitude , Longitude FROM dbo.DecodedCSVMessages_Staging WHERE Message_ID IN (1, 3) ) , details AS ( SELECT MMSI , Ship_Type , Vessel_Name , Row_Number() OVER (PARTITION BY MMSI ORDER BY "Time" DESC) As row_num FROM dbo.DecodedCSVMessages_Staging WHERE Message_ID = 5 ) SELECT all_positions.MMSI , all_positions.Message_ID , all_positions."Time" , details.Ship_Type , details.Vessel_Name , all_positions.Latitude , all_positions.Longitude FROM positions INNER JOIN details ON details.MMSI = positions.MMSI AND details.row_num = 1 -- Limit to "latest" ship details per MMSI INNER JOIN all_positions ON positions.MMSI = all_positions.MMSI </code></pre> <p>EDIT (after feedback from Clockwork-Muse):</p> <p>Your original query will return duplicate rows when a ship reports more than once from within the desired area. To get rid of this, just use DISTINCT in the positions CTE:</p> <pre><code>; WITH positions AS ( SELECT DISTINCT MMSI , Message_ID , "Time" , Latitude , Longitude FROM dbo.DecodedCSVMessages_Staging WHERE Message_ID IN (1, 3) AND Latitude &gt; 55 AND Latitude &lt; 85 AND Longitude &gt; 50 AND Longitude &lt; 141 ) , all_positions AS ( SELECT MMSI , Message_ID , "Time" , Latitude , Longitude FROM dbo.DecodedCSVMessages_Staging WHERE Message_ID IN (1, 3) ) , details AS ( SELECT MMSI , Ship_Type , Vessel_Name , Row_Number() OVER (PARTITION BY MMSI ORDER BY "Time" DESC) As row_num FROM dbo.DecodedCSVMessages_Staging WHERE Message_ID = 5 ) SELECT all_positions.MMSI , all_positions.Message_ID , all_positions."Time" , details.Ship_Type , details.Vessel_Name , all_positions.Latitude , all_positions.Longitude FROM positions INNER JOIN details ON details.MMSI = positions.MMSI AND details.row_num = 1 -- Limit to "latest" ship details per MMSI INNER JOIN all_positions ON positions.MMSI = all_positions.MMSI </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POSQL Query Adjustment
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USStevieG
    1. USStevieG
    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. This table or related slice is empty.
    1. COUnfortunately, this version of the query is flawed - if there is more than one report from inside the given latitude/longitude, you'll get a Cartesian product. This is one time I recommend the use of the `DISTINCT` clause (inside the `positions` CTE - oh, and the lat/long from there aren't referenced in the final `SELECT`, either).
      singulars
      1. PO
      1. USClockwork-Muse
    2. COActually, no, you won't get a cartesian product. I do agree, however, that you would get duplicate rows. However, I based my answer on the assumption that the output from the original query was what the OP wanted, which is what he explicitly stated..
      singulars
      1. PO
      1. USStevieG
    3. COIt is to be expected that there will be more then one report within the given latitude/longitude for each MMSI. I need every record that occurs there. Each MMSI represents a ship at a given point (lat and lon). In essence, reoccuring MMSI numbers within my study area will show me where a given ship has been.
      singulars
      1. PO
      1. USdpalm
 

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