![]() ![]() Replaces the text in a new worksheet with a statement from the historical archive that SQL Developer maintains. You can highlight a section of code and these keystrokes toggle comments on/off for the entire block.ģ) SQL History (CTRL+Up, CTRL+Down). To save moving your hands from the keyboard to use the mouse to click on the toolbar buttons, the following accelerators are in place by default:Ģ)ělock Comment (CTRL + /). These can be re-configured to your personal preference from Tools > Preferences > Accelerators.ġ) Toolbar Shortcuts. ‘Accelerators’ is Oracle-speak for keyboard shortcuts. Hopefully you’ll agree that the code on the right is considerably easier to read than the same code on the left. Uncheck ‘Enable highlight’ against Current SQL.Remove the bold highlight from ‘Default Element Name’ and ‘Default Keyword’.I normally make the following changes (Tools > Preferences > Code Editor > Syntax Colours): Picking a better colour scheme eases readability as you’ll be able to pick out strings, operators and brackets/braces quicker but the delivered scheme highlights keywords in bold, which throws out the alignment if you’ve pick a fixed-width font. This setting is independent of the Windows Clear-Type setting in Display Properties.ģ) Syntax Colours. To turn it on, go to Preferences > Code Editor > Display > Enable Text Anti-Aliasing. Some believe it makes the code more readable, while others believe it makes the text too blurry. Why deliver the product with a default font that isn’t fixed width, therefore making this harder? The first change I make is to swap the font (Tools > Preferences > Code Editor > Fonts) for Lucida Console, 11pts – although the font size may vary depending upon monitor resolution and the state of your eyesight.Ģ)Ğnable Anti-Aliasing. Developers like to indent and line up their code to make it more readable. I make the following changes:ġ)Ĝhange the Font. It’s possible that you’ll think otherwise (opinions differ wildly when it comes to code formatting, whitespace, code in upper or lower case etc) but I think that by default the code editing window is unattractive. (Based on SQL Developer v1.5.3 on WinXP) Setup tweaks to make SQL Developer easier on the eye I’ve listed below a combination of tips/tricks and improvements to the default configuration that have made me more productive. I use it principally for SQL development (not PL/SQL, Reporting etc) so I don’t use the entire set of functionality that the product offers, but there are a few things I’d change. Improving product though it is, it’s not perfect. There are other SQL Editors out there – both free and commercial – but given that SQL Developer is free, cross-platform (can run on Windows/Linux/Mac etc), cross-database (can also be used against SQL Server, MySQL etc) and has the weight of Oracle behind it there’s a good chance of it’s usage spreading rapidly. It has been improving and maturing over the last couple of years and it really does feel like it’s a reasonable competitor now. It’s Oracle’s free database development IDE with a more user-friendly UI than SQL Plus and taking aim at Quest Software’s TOAD. The team can also create and share a common style, to be applied to all code just before committing it to the shared source control repository. If everyone's code is formatted the same way, it will be much easier for any team member to review another’s code with minimal confusion.If you’re a PeopleSoft developer working on an Oracle Database you’ve probably come across Oracle’s SQL Developer product by now. A developer can very quickly view any code in the style they find easiest to read. With a few keyboard strokes ( Ctrl K, Ctrl Y mnemonic " kick yourself"), we run the Format SQL command, which will apply the current Active Style to all code, or selected code, within an SSMS query window. SQL Prompt allows us to define custom or built-in styles, where each style (akin to a template), encapsulates a specified set of values for the formatting options that govern how you wish to lay out your SQL code. If we remove all formatting from a piece of code, it will continue to function exactly as before. Formatting or style changes are 'decorative' changes that affect only whitespace, such as line breaks, tabs and spaces they do not change the meaning of that code in any way. ![]() Formatting and styles are all about taking some code and making sure that it is easy to read and understand. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |