By default, after PLSQL Developer logs in, All objects will be selected in Brower. If the user you log in is dba, to expand the tables directory, it normally takes a few seconds to wait. The response rate is calculated in milliseconds after selecting My Objects.
Setting method:
Tools menu --> Brower Filters, the order window of Brower Folders will be opened, and "My Objects" can be set as the default.
Tools menu - Brower Folders, move several directories you often click (for example: Tables Views Seq Functions Procedures) a little higher, and add color distinctions, so that your average table search time will be greatly shortened, try it out .
2. Remember passwords
This is a controversial feature because remembering passwords can bring data security issues. But if it is a library for development, the password can even be the same as the user name. It is meaningless to enter the password every time. You can consider letting PLSQL Developer remember the password.
Setting method: Menu Tools --> Preferences --> Oracle --> Logon History --> Store With Password
3. Double-click to display table data (verified and available)
The default response when double-clicking a table or view with the mouse is really disappointing , because what I care about most is the table structure and data, but after double-clicking, neither of these two things happened. Maybe the default response is what the experts need, but for me, viewing the data and table structure is the most important thing. Do not care. But the good thing is that this can be set, you can bind the required events to the mouse double-click and drag-and-drop, such as: double-click to edit data, drag-and-drop to display the table structure, Yeah!
Setting method: menu Tools --> Preferences --> Browser, on the right, bind double-click (Double-Click action) and drag and drop (Drag & Drop action) for different Object Types (such as selecting Table).
4. It is a good habit to use all uppercase characters in SQL statements
. The core of the information system is the database. When there is a problem with the system, the first thing to check is the SQL statement. How to quickly find that SQL statement in the vast log is a pain. thing. All-caps SQL statements won't solve this problem completely, but it's relatively easy to find a line of all-caps characters in the middle of a bunch of code, and your eyes will thank you. Setting method: Menu Tools --> Preferences --> Editor --> Keyword Case --> Uppercase 5. SQL statements written in SQL Window by special Copy usually need to be placed in Java or other languages, and they need to be converted into Add the corresponding hyphen to the string, this one thing does not need to be repeated, right-click on the written SQL, use the special Copy and that is OK! Setting method: Right mouse button --> Special Copy 6. Custom shortcut keys There are many keys reserved in PLSQL Developer for users to customize, which is a very high thing. Unlike the overbearing Word, basically all the keys have predefined functions, and it is a headache to modify. Under normal circumstances, after opening PLSQL Developer, the most common thing is to open SQL Window and Command Window, and define shortcut keys for these two operations, ALT+S and ALT+C, so that three clicks with the mouse only need Press the key. Setting method: menu Tools --> Preferences --> Key Configuration
7. In the SQL Window, the setting method of the statement is automatically selected according to the cursor position
: Preferences --> Window Types --> SQL Window, just select the AutoSelect statement. Note that a semicolon is required after each statement.
8. Start PLSQL Developer, the window list menu will be automatically called up
Two-step settings are required. First, save the desktop settings, and then check the Window list option. The specific operations are as follows:
a. Select Option in the User Interface in the Preference option under the Tools menu item, and put the front in the Autosave desktop on the right. check box is checked.
b. Check the Window list option under Tools in the menu item.
9. Format SQL (format)-PL/SQL beautifier (verified and available)
When you get a long SQL statement and want to quickly check the logic in it, you can put it in this tool, format it, and the logic of the statement will be clear at a glance
10. The database automatically detects the connection status
Because the database is automatically disconnected after a period of inactivity, and then you need to manually connect yourself, because of network reasons, it will always be stuck there. The tool provides the function to detect the connection and can connect automatically.
The specific settings can be checked in front of Tools-Preferences-Check connection, Check connection.
11. Commonly used shortcut keys
In fact, these are mentioned in item 6, and the following are my customary settings:
ctrl+tab switch windows window (or alt+left/right)
alt + n to create a new sql window
alt + c closes the current window
alt + f format sql
alt + end list all results
shift + esc stop running
Replenish:
12. Differences between two databases (compare the structure of tables, views, functions, sequences)
Log in to the target library (new library), select Tools --> Compare User Objects, select the old library for Target Session, and then compare the objects with differences and update SQL (SQL can be saved as Command File, and the user can log in to the old library by changing the user). , open and execute).
13. Execute a single SQL statement
When using the SQL Window of PL/SQL Developer, press the F8 key, PL/SQL Developer executes all SQL statements in the window by default, and needs to be set to the SQL statement where the mouse is, that is, execute the current SQL statement;
Setting method: PL/SQL Developer 7.1.2 -->tools->Preferences-->Window types, check "AutoSelect Statement".
14. View the execution plan
When using the SQL Window of PL/SQL Developer, sometimes the efficiency of the input SQL statement execution, analyze the structure of the table below, how to improve the efficiency of the query, you can check the execution plan provided by Oracle;
How to use: Select the SQL statement to be analyzed, and then click the Explain plan button (that is, the execution plan) on the toolbar, or press F5 directly.
15. Debugging stored procedures
When using PL/SQL Developer to operate Oracle, sometimes some stored procedures are called, or stored procedures are debugged;
How to call a stored procedure: First, select Procedures in the Browser on the left of PL/SQL Developer to find the stored procedure to be called; then, select the stored procedure to be debugged, right-click, select Test, and in the pop-up Test script window, For parameters defined as in type, you need to enter a value for the Value of the parameter; finally click the number button above: Start debugger or press F9; finally click: RUN or Ctrl+R.