they showed up in 18.1 because we fixed a bug where they were being suppressed
they can show errors, warnings, and parser insight messages - mouse over the colored block, and it'll show you what's what
Hi Jeff, Thanks for the quick reply. If you fixed a bug that was suppressing it, that explains why I just noticed it. When I hover the mouse, I can see the window pop out that shows the SQL statement, but there is no error or warning message in the window. When I run the code that's referenced, it runs without error. Is the color meaningful, e.g. warning vs error. Is there a legend?
Sorry, but I'm still confused as to what it's trying to tell me.
Is the color meaningful, e.g. warning vs error. Is there a legend?
I suggest you use that as a 'learning' experience and see what you can find out by testing.
1. use a valid query
2. use a query that produces errors
Don't be afraid of breaking sql dev by actually TRYING things.
Post a screenshot?
The area next to the scroll bar is called "file overview margin". It is supposed to give 30000 feet (sorry, meters) view of the code, which is especially helpful for large sql scripts or pl/sql modules. By mouse clicking on problematic rectangle, it would scroll the view to the actual error/warning/suggestion. Then put mouse over the squiggle lines in the text, and that popup would actually be more informative.
Thanks all for responding. I followed the suggestions about hovering over the block to see the statement, then clicking on the colored block to navigate to the "problem" statement. I can now see the squiggle line under the "problem" table. When I hover over the "problem" table, I see the error message "Undefined Table".
The issue is the table is not undefined and both Describe (F4) and running the statement work fine, without errors. I tried to further qualify the table by prefixing with the schema name, but that didn't seem to change things. See attached screenshots.
We check the data dictionary for your object, if we don't find it, we warn you
select owner,object_name from all_objects
where object_type in ('TABLE','VIEW','SYNONYM')
and object_name in (?)
Is it there? If so, what is exactly 'SKUPLANNINGPARAM' ?
then it shouldn't be showing that way, can you share the entire query?
Here's an example of one of the queries in the worksheet that is highlighted. There are multiple queries that reference the same table that are also highlighted as errors.
--SKUs with EOQ > Order Multiple - Detail by SKU
select /*+ parallel(10) */ i.u_opstudy, s.item, i.u_wic_label, d.inddmdunitcost,
s.loc, s.mindrpqty, s.incdrpqty, (case when mindrpqty>incdrpqty then 1 else 0 end) eoq
from skuplanningparam s, skudemandparam d, loc l, udt_itemparam i
where s.item = i.item
and s.loc = l.loc
and s.item = d.item
and s.loc = d.loc
and l.loc_type = '6'
and s.externalskusw = '0'
and s.item = '40000216322'
order by u_opstudy, item, loc;
But you aren't showing the ENTIRE worksheet that has the colors you are asking about.
We need to see the WHOLE thing.
yes, a screenshot would be good
but we're not showing you errors, we're showing you potential issues via the parser, so you can AVOID errors.
If we're giving a false positive on non-existent table, I'd like to fix that
1. What if you temporarily erase everything except that query, is the false positive still there?
2. What if you restart sqldev, paste this query into an empty worksheet?
If experiment #1 or #2 didn't work, can you please share what is in the statements log?
Per your suggestion, I tested a few different scenarios:
1) Erasing everything in the worksheet and running the query, the false positive is still there
2) Close and restart SQLDev pasted query into new blank worksheet, no false positive on the table
3) Go back to the original worksheet and run original query, no false positive on the table
4) Close and restart SQLDev and run original query in original worksheet, false positive returns
5) Paste query into new blank worksheet, false positive exists in new worksheet
Let me know if there is anything else I can provide.