By default, it is bound to the Ctrl+Alt+O key combination, and is also available via a main toolbar button as well as in the main File->Quick File Open menu. You can also use the Quick File Open feature to open recent files as well as Bookmarks and History entries. How many recent files to keep track of can be specified in the Tool Properties dialog, in the SQL Commander category under then General tab. The File->Open Recent submenu lists the recently loaded files. When you close the SQL Commander tab or exit DbVisualizer, you are asked what to do if there are any pending edits that need to be saved. The editor tracks any modifications and indicates changes with an asterisk (*) after the filename.
DBVISUALIZER FORMAT SQL FULL
The name of the loaded file is listed in the status bar of the editor, with the full file path shown in the window title. Loading a file loads it into a new SQL Commander tab or activates the tab that already holds it. Use the standard file operations, Open, Save and Save As in the File main menu or the main toolbar to accomplish this. The SQL editor supports loading statements from a file and saving the content of the editor to a file. You can also change the SQL Editor font family, which is useful and necessary in order to display characters for languages like Chinese, Japanese, etc., in Tool Properties in the Appearance/Fonts category to set the font for the SQL Editor. The editor uses the Tool Properties settings from the SQL Commander/Comments category under the General tab to detect comments.
DBVISUALIZER FORMAT SQL HOW TO
You can change how to display the different kinds of words, as well as the editor selection background color, the current line highlight color and the editor background color, in the Tools->Tool Properties dialog, in the Appearance/Fonts category. For instance, keywords are displayed with a bold blue font, while quoted text is displayed with a regular type red font. To make it easier to see at a glance what is what, the SQL Editor displays words using different font styles depending on their classification. Syntax Color CodingĪn SQL script consists of keywords, operators, object identifiers, quoted text, etc. These are described in the following sections.
But it also offers additional features to help you specifically with editing SQL scripts. The SQL Editor is like any editor you're used to when it comes to typing, scrolling etc. An asterisk after the filename indicates that there are unsaved edits. If you just type into the editor without loading a file, the filename "Untitled" is shown instead.
First the character encoding and then the filename. The last two fields show information about the file loaded in the editor, if any. Next comes the Auto Commit Status field, showing whether Auto Commit is enabled. The next field shown in the screenshot is only visible when working with macros, described in the Recording and Playing Edit Macros section. You can toggle this mode using the Toggle Typing Mode keyboard shortcut, by default bound to the Insert key. The next field in the Status Bar shows INS if characters you type will be inserted at the caret position or OVR if they will overwrite the current text at the caret position.
This can be useful when you get an error message executing a script that contains this information rather than a line/column location. The last figure, within square brackets, is the caret position from the top. The first field shows the current caret position in the format: The editing related buttons are covered below.īelow the editor, you see a Status Bar. Above the editor is a toolbar with buttons related both to execution of scripts and to editing.
0 kommentar(er)
