If the script is a query console, click the tab of this query console.įrom the main menu, select Tools | External Tools | sqlite3. Clicking the Insert Macros… icon will open the Macros dialog that lists all available macros and their values.Ĭlick OK to add the tool and then apply the changes.ĭouble-click the script file to open it in the editor. You can use macros that can refer to the project name, the current file path, and so on. In our case, sqlite3 will be run with sqlite.db ".read '$FilePath$'" arguments. For example, you can point this field to a folder with the database file ( /Users/jetbrains/DatagripProjects/sqlite). Working directory: the path to the current working directory from which the tool is executed. For example, sqlite.db ".read '$FilePath$'" Use a backslash to escape double quotes that are part of the argument or path. Use double and single quotes for arguments and paths that contain spaces. Use spaces to separate individual arguments. For example, /Users/jetbrains/DatagripProjects/sqlite/sqlite3.Īrguments: the arguments passed to the executable file, as you would specify them on the command line. Program: the path to the application executable file. For example, Command-line tool for SQLite. You can select an existing group or type the name of a new group.ĭescription: a meaningful description of the tool. Group: the name of the group to which the tool belongs. Name: the name of the tool that will be displayed in the DataGrip interface. Open settings by pressing Ctrl Alt S and navigate to Tools | External Tools.Ĭlick the Add button ( ) and specify the following settings: This configuration will pass contextual information from your project to sqlite3 as command-line arguments and display the output in the Run tool window. To run the script, you need to create a configuration for a third-party tool (in our case, sqlite3). And use the following script in the SQL file. You can create similar configurations for other tools.įor this tutorial, we will create the sqlite.db database file in /Users/jetbrains/DatagripProjects/sqlite. In this topic, we are going to use the sqlite3 as an example. By default, meta-commands are highlighted in green. It means that you can open an SQL script with meta-commands in the editor, but you need an external tool to run the script. CLI tools do this translation.ĭataGrip supports syntax highlighting for meta-commands but not the translation logic. These commands are not standard SQL commands that your database would easily understand. For example, sqlplus has DESCRIBE psql has backslash directives like \dD in sqlcmd, you can use :r Script.sql to load a script file. Other tools have different meta-commands. When you issue the dot-command, sqlite3 uses its own interpretation of the command and runs it on a database. These dot-commands are used to change the output format of queries or to execute certain prepackaged query statements. For example, in SQLite, except for ordinary SQL statements, you can use dot-commands. Meta-commands use special syntax that is specific for every tool. Standard commands are SELECT, CREATE, UPDATE, and other ordinary SQL commands. In the majority of cases, these tools support two types of commands: standard and meta. Oracle: sqlplus (SQL Command Line for SQL*Plus) The following list shows you a couple of examples. Almost every database vendor has its own Command-Line Interface (CLI) tool.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |