So if we click on this, it's going to analyze this code that's currently in the editor. To the left of that, we can see Code Analysis in the Editor window. So this is where we change how the editor views the rule sets. So as we select different rules sets, we can see, in the case of this code, most of the violations go away when I choose Code Correctness. But essentially, you have to choose the rule set that is best for your organization. So at the top in the toolbar, we have the rule sets, which we'll talk briefly in a minute. So for instance, if you were unfamiliar with the category SQL, you could click on it and it will give you all the information on the different categories, including SQL, so you can better understand what is meant when the tool says SQL. This gives a more thorough breakdown of the actual rule violation itself, and it also gives information on each one of the categories. As we can see, I have various options for ignoring it, or I can choose explain details. So if I right click on one of these, and I choose Code Analysis Violation at the top, and then choose the rule. So as I hover over them, we can see the rule violation pop up, and it gives a breakdown of the rule, the code element, and the severity of the violation. So on screen, I have the editor open, and we can see blue wavy lines under certain parts of the code. The best time to adopt coding standards is during development, which is why I've started with the Editor in Toad for Oracle.
Code analysis helps ensure that your code meets, and exceeds, your company's best practice standards for performance, maintainability, and reliability.
Today, we will discuss code analysis in Toad for Oracle. Hello, my name is Robert Pound, and I am a Product Technologist for Quest.
0 kommentar(er)
