(SELECT lpad(trunc(sum(prt.hours)*100),6,'0')
FROM prod.prtime prt
WHERE( prt.tr_date >= add_months(trunc(sysdate, 'mm'),-12)
AND prt.tr_date < trunc(sysdate) )
and prt.pay_sum_grp in ('REG', 'REGH','OT','ED','OREN')
-- and prt.employee = 19330
and emp.company = prt.company (+)
and emp.employee = prt.employee (+)
group by prt.employee ) HOURS_WORKED
For the most part, all the values come across. The issue I'm having is if the value is 0, a blank is being displayed instead of the 0.
Is there anything I can do to ensure that the 0's appear.
I've attached a file with the results I'm getting. Blanks.docx
SQL> select lpad(nvl(1*100,'0'),6,'0') from dual;000100SQL> select lpad(nvl(null*100,'0'),6,'0') from dual;000000SQL> select lpad(nvl(0*100,'0'),6,'0') from dual;000000
Check what is coming back. Query both and for one of the 'blank' ones, provide the dump output.
lpad(nvl(trunc(sum(prt.hours)*100),'0'),6,'0'), dump(lpad(nvl(trunc(sum(prt.hours)*100),'0'),6,'0'))
Mark Geerlings
I agree with slightwv, it must be either a null value on a record, or a complete lack of matching records (which results in a null). So you may need an nvl around this entire sub-query.
I queried a couple of the blanks using just the sub-w and I get no records returned.
I attached a screenshot of the results.
The results are correct because these are new employees and would not have accumulated any working hours just yet.
Question is how can I have the value of 000 display for these new hires? Blanks2.docx
slightwv (䄆 Netminder)
If the SUM returns a null value, the code I posted will provide '000000'. The blanks in the result set have to be nulls. I really don't see a way around it.
NOW, if you are running code outside of that query and the query itself is returning an empty result set, you need to handle that in the app making the query.
You really can't make a query return a row when there are no rows found. Well, you can but it isn't pretty.
You should handle the 'no rows found' in the app not in the SQL.
metalteck
ASKER
That's exactly the problem now, since the records are null, nothing is being returned in the main query. Since I'm using sql developer, how would I handle that in the app instead of the sql?
Would using a case statement be a not so pretty way of hard-coding 00000 whenever there is a null found?
Wrapping the select will work but I think there is a bigger issue.
Based on the sample results you have and what you gave as the reason for the blank lines, you have to have one massive script that executes many different select statements.
If that is the case, my experience tells me that you probably have chosen the wrong solution to your overall requirements.
If the individual select statements are hitting the same tables over and over again, yes, you have chosen the wrong solution for a few reasons.
Post more about what you are hoping to accomplish and we can probably help get you to where you should be.