Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <h3>Standard SQL solution</h3> <p>To get <em>two separate rows</em> (as later specified in the Q update) use a <a href="http://www.postgresql.org/docs/current/interactive/sql-select.html#SQL-UNION" rel="nofollow"><strong><code>UNION</code></strong></a> query: </p> <pre class="lang-sql prettyprint-override"><code>SELECT 'old' AS version, t1.id, t1.field1, t1.field2 FROM table1 t1 JOIN table2 t2 ON t2.table1_original_id = t1.id WHERE t2.id = $some_t2_id -- your t2.id here! UNION ALL SELECT 'new' as version, t1.id, t1.field1, t1.field2 FROM table1 t1 JOIN table2 t2 ON t2.table1_new_id = t1.id WHERE t2.id = $some_t2_id; -- your t2.id here! </code></pre> <p>Note: this is <em>one</em> query.<br> Returns as requested, plus a column <strong><code>version</code> to distinguish the rows</strong> reliably:</p> <pre class="lang-sql prettyprint-override"><code>version | id | field1 | field2 --------+----+--------+-------- old | 3 | blah | stuff new | 11 | more | things </code></pre> <h3>Faster Postgres-specific solution</h3> <p>A more sophisticated, but shorter and faster solution:</p> <pre class="lang-sql prettyprint-override"><code>SELECT version, id, field1, field2 FROM ( SELECT unnest(ARRAY['old', 'new']) AS version ,unnest(ARRAY[table1_original_id, table1_new_id]) AS id FROM table2 t2 WHERE t2.id = $some_t2_id -- your t2.id here! ) t2 JOIN table1 USING (id); </code></pre> <p>Same result.</p> <p><a href="http://sqlfiddle.com/#!11/3859e/8" rel="nofollow">-> SQLfiddle demo for both.</a></p>
    singulars
    1. This table or related slice is empty.
    1. POSQL Select Query - "Pairing" Records Together
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USErwin Brandstetter
    1. USErwin Brandstetter
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POSQL Select Query - "Pairing" Records Together
      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. VTAcceptedByOriginator
    1. COThis query returns zero records... unless I take the WHERE clause out - I'll have to do some more testing but this will either work or get me very close. Out of curiosity, what's the deal with the WHERE? ... = 1? The records in Table2 won't always be ID 1 and I don't actually need that field. Maybe you see/know something I don't! :) I had a hunch UNION was a part of the solution but was failing at making it happen. Thanks.
      singulars
      1. PO
      1. USuser1801810
    2. COThat's to manually pair them.
      singulars
      1. PO
      1. USHart CO
    3. CO@user1801810: `1` would be `table2.id`. Also added a faster, Postgres-specific version
      singulars
      1. PO
      1. USErwin Brandstetter
 

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