Databases
StackOverflow2013
Postsdbo
PODjango order_by causes LEFT JOIN
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODjango order_by causes LEFT JOIN
    primarykey
    data
    text
    <p>Can anyone tell me why when I add the <code>order_by()</code> the query that gets output changes from a <code>INNER JOIN</code> to an <code>LEFT OUTER JOIN</code>? </p> <p>Is there any way to preserve the <code>INNER JOIN</code>-ness?</p> <pre><code>data = models.RetailSalesFact.objects.values('customer_key__customer_state', 'date_key__calendar_month_name') data = data.filter(date_key__calendar_year=year) data = data.annotate(sales=Sum('sales_quantity')) data = data.order_by('date_key__calendar_month_name') </code></pre> <p><strong>Before:</strong></p> <pre><code>SELECT Customer_Dimension.Customer_State, Date_Dimension.Calendar_Month_Name, SUM(Retail_Sales_Fact.Sales_Quantity) AS sales FROM Retail_Sales_Fact INNER JOIN Customer_Dimension ON (Retail_Sales_Fact.Customer_Key = Customer_Dimension.Customer_Key) INNER JOIN Date_Dimension ON (Retail_Sales_Fact.Date_Key = Date_Dimension.Date_Key) WHERE Date_Dimension.Calendar_Year = ? GROUP BY Customer_Dimension.Customer_State, Date_Dimension.Calendar_Month_Name ORDER BY Date_Dimension.Calendar_Month_Name ASC </code></pre> <p><strong>After:</strong></p> <pre><code>SELECT Customer_Dimension.Customer_State, Date_Dimension.Calendar_Month_Name, SUM(Retail_Sales_Fact.Sales_Quantity) AS sales FROM Retail_Sales_Fact INNER JOIN Customer_Dimension ON (Retail_Sales_Fact.Customer_Key = Customer_Dimension.Customer_Key) LEFT OUTER JOIN Date_Dimension ON (Retail_Sales_Fact.Date_Key = Date_Dimension.Date_Key) WHERE Date_Dimension.Calendar_Year = ? GROUP BY Customer_Dimension.Customer_State, Date_Dimension.Calendar_Month_Name ORDER BY Date_Dimension.Calendar_Month_Name ASC </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USLeopd
    1. USAl W
    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. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODjango order_by causes LEFT JOIN
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PODjango order_by causes LEFT JOIN
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PODjango order_by causes LEFT JOIN
      1. USDZ.
      1. VTFavorite
    1. COAnswer updated...
      singulars
      1. PODjango order_by causes LEFT JOIN
      1. USFallenAngel
 

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