Searching for Null Values IN DataAssist

Hi,

I ran the search wizard for DataAssist and then joined two tables, created a date range and included some AS statements.

Here is what my query currently looks like:

SELECT inventory.itemId AS Item_ID, inventory.itemName AS Item, inventory.itemDesc AS Description, inventory.itemSize AS Size, inventory.itemColor AS Color, inventory.partNum AS Part_Number, inventory.prodLine AS Product_Line, inventory.itemPrice AS Price, inventory.itemQty AS Quantity_Available, (inventory.itemQty*inventory.itemPrice)AS Total_Value_of_Available, SUM(orderdetails.DetailQuantity)AS Quantity_Sold, SUM(orderdetails.DetailQuantity*inventory.itemPrice)AS Total_Value_of_Usage
FROM orderdetails INNER JOIN inventory ON orderdetails.DetailItemId = inventory.itemId INNER JOIN orders ON orderdetails.DetailOrderId = orders.OrderId
GROUP BY inventory.itemId
ORDER BY inventory.itemName ASC

My issue is, how to have items that were not sold during the selected date range, to also appear on the results page? So...if there was not a particular Part_Number listed from the orderdetails table, during the date range that was selected, but still listed in inventory, it would still show up on my results page.

Can you please advise me as to how to search for "NULL" values and still have them appear?

Thanks!

Do a LEFT OUTER JOIN instead of an INNER JOIN

Hi.

Thanks, that kind of worked. It is showing all items (even the ones that did not sell, which is good), but only when I don't put in a date range. When I put in a date range, it is still only viewing the items in my inventory that sold for that date range. I need it to list all items in inventory even if it didn't have a sell in that date range.

Here is my query now:

SELECT inventory.itemId AS Item_ID, inventory.itemName AS Item, inventory.itemDesc AS Description, inventory.itemSize AS Size, inventory.itemColor AS Color, inventory.partNum AS Part_Number, inventory.prodLine AS Product_Line, inventory.itemPrice AS Price, inventory.itemQty AS Quantity_Available, (inventory.itemQty*inventory.itemPrice)AS Total_Value_of_Available, SUM(orderdetails.DetailQuantity)AS Quantity_Sold, SUM(orderdetails.DetailQuantity*inventory.itemPrice)AS Total_Value_of_Usage
FROM orderdetails RIGHT OUTER JOIN inventory ON orderdetails.DetailItemId = inventory.itemId LEFT OUTER JOIN orders ON orderdetails.DetailOrderId = orders.OrderId
GROUP BY inventory.itemId
ORDER BY inventory.itemName ASC

And here is how my date range is set up:

$WADbSearch1->addComparisonFromEdit("OrderDate","S_OrderDate","AND",">=",2);
$WADbSearch1->addComparisonFromEdit("OrderDate","E_OrderDate","AND","<=",2);

I found the above method for date range in another thread here in the DataAssist forum.

What am I doing wrong?

Thanks!

I think you add:

$WADbSearch1->addComparison("OrderDate","NULL"," OR","IS",2);

Thanks Ray, but that still returned the same results. Any other ideas?

Do you think possibly the way I coded my date range is incorrect?

What is the final query that is running? I think I'd start by analyzing what is wrong with it to figure out what to change in the code that controls it.

Hi,

I did try that. I have even built the query in a separate query builder that will tell me if I have an error. I am still thinking it is somewhere in the PHP code for the date range.

My code for the date range now looks like this:

//comparison list additions
$WADbSearch1->addComparisonFromEdit("OrderDate","S_OrderDate","AND",">=",2);
$WADbSearch1->addComparisonFromEdit("OrderDate","E_OrderDate","AND","<=",2);
$WADbSearch1->addComparison("OrderDate","NULL","OR","IS","<=>",2);

And my query looks like this:

SELECT inventory.itemId AS Item_ID, inventory.itemName AS Item, inventory.itemDesc AS Description, inventory.itemSize AS Size, inventory.itemColor AS Color, inventory.partNum AS Part_Number, inventory.prodLine AS Product_Line, inventory.itemPrice AS Price, inventory.itemQty AS Quantity_Available, (inventory.itemQty*inventory.itemPrice)AS Total_Value_of_Available, SUM(orderdetails.DetailQuantity)AS Quantity_Sold, SUM(orderdetails.DetailQuantity*inventory.itemPrice) AS Total_Value_of_Usage
FROM orderdetails RIGHT OUTER JOIN inventory ON orderdetails.DetailItemId = inventory.itemId LEFT OUTER JOIN orders ON orderdetails.DetailOrderId = orders.OrderId
GROUP BY inventory.itemId
ORDER BY inventory.itemName ASC

Your suggestion almost worked, but it wouldn&#8217;t return anything. Through testing I found that $WADbSearch1->addComparison("OrderDate","NULL","OR","IS","<=>",2); works, but when I want to view all items without any date range, it is now returning just 123 rows, but there is 253 rows in my inventory table. I can&#8217;t figure out why it isn&#8217;t picking up the other 130 items.

When I take out the line $WADbSearch1->addComparison("OrderDate","NULL","OR","IS","<=>",2); it returns all items when I DO NOT enter a date range, but then when I do enter a date range search it does not pick up unsold items.

I have also tried the date range like this:

//comparison list additions
$WADbSearch1->addComparisonFromEdit("itemName","S_itemName","AND","Includes",0);
$WADbSearch1->addComparisonFromEdit("itemDesc","S_itemDesc","AND","Includes",0);
$WADbSearch1->addComparisonFromEdit("itemPrice","S_itemPrice","AND","Includes",0);
$WADbSearch1->addComparisonFromEdit("itemQty","S_itemQty","AND","=",1);
$WADbSearch1->addComparisonFromEdit("partNum","S_partNum","AND","Includes",0);
$WADbSearch1->addComparisonFromEdit("prodLine","S_prodLine","AND","Includes",0);
$WADbSearch1->addComparison("orders.OrderDate","".((isset($_GET["S_OrderDate"]))?WAQB_getEndDate($_GET["E_OrderDate"]):"") ."","AND","<=",2);

But this one is not picking up any null values period. Can I maybe add something at the end of this line to make it return null values within the date range? I have tried several combinations with no luck.

Any help would be appreciated.

You have to debug and figure out the correct SQL statement and where clause you want and how to get dbsearch to create that where clause.

You should be able to echo and die to show the full query you are running and figure out what is wrong and how to fix it. You may want to consider paying for a webassist support incident and one of our engineers could help you through this over the phone.