NOTE: This article is 3 years or older so its information may no longer be relevant. Read on at your own discretion! Comments for this article have automatically been locked, refer to the FAQ
for more details.
So I've been using SQLDeveloper like mad lately and have been finding some really neat features that it provides. One of the great time savers is its ability to create persistent highlights that you can use to instantly see the patterns in data. Great for debugging that ETL!
This is what I mean by the highlights, in this case I was looking at a table of test results and wanted to see which ones were failed, without a highlight I had to strain my eyes and look at each word, with the highlight, it's like magic, the failed tests just pop out instantly!
So how do you turn this amazing feature on?
When looking at results/data simply right click and select 'Find/Highlight...'
This brings up a dialogue box, in my case I typed in 'fail' in the, ticked 'Whole Word' and 'Persist Highlight' and chose a red colour to display the cell with.
This will save the highlight for good, it can be removed later by clicking the X button in the same dialogue box next to the previously persisted highlight.
There is a bit of a bug I found with the highlight colour selector on OS X however, it seems that when you click to select a colour, the entire dialogue box disappears. The way to get around this is to click the down arrow on the colour selector and use arrow keys to select the colour instead.
Hope you found this post useful...
...so please read on! I love writing articles that provide beneficial information,
tips and examples to my readers. All information on my blog is provided free of
charge and I encourage you to share it as you wish. There is a small favour I ask in return however -
engage in comments below, provide feedback, and if you see mistakes let me know.
If you want to show additional support and help me pay for web hosting and
domain name registration,
donations, no matter how small, are always welcome!
Use of any information contained in this blog post/article is subject to this disclaimer
Other posts you may like...