CLICurrent database: %1現在のデータベース: %1No current working database is set.現在の作業データベースが設定されていません。Type %1 for help%1と入力してヘルプを表示Database passed in command line parameters (%1) was already on the list under name: %2コマンドラインパラメータ(%1) で渡されたデータベースは既に%2のリストにありましたCould not add database %1 to list.データベース %1 をリストに追加できませんでした。closed閉じましたCliCommandUsage: %1%2使用方法: %1%2CliCommandAddCould not add database %1 to list.データベース %1 をリストに追加できませんでした。Database added: %1データベース%1を追加しましたadds new database to the list新しいデータベースをリストに追加Adds given database pointed by <path> with given <name> to list the databases list. The <name> is just a symbolic name that you can later refer to. Just pick any unique name. For list of databases already on the list use %1 command.<パス>が指す特定のデータベースを追加します。 与えられた<名前> のデータベースのリストを一覧表示します。<名前> は、後で参照できる単なる記号名です。 一意の名前を選択してください。 すでにリストにあるデータベースを表示するには、%1コマンドを使用してください。nameCLI command syntax名前pathCLI command syntaxパスCliCommandCdChanged directory to: %1ディレクトリを %1に変更しましたCould not change directory to: %1ディレクトリを%1に変更できませんでしたchanges current working directory現在の作業ディレクトリを変更Very similar command to 'cd' known from Unix systems and Windows. It requires a <path> argument to be passed, therefore calling %1 will always cause a change of the directory. To learn what's the current working directory use %2 command and to list contents of the current working directory use %3 command.Very similar command to 'cd' known from Unix systems and Windows. It requires a <path> argument to be passed, therefore calling %1 will always cause a change of the directory. To learn what's the current working directory use %2 command and to list contents of the current working directory use %3 command.pathCLI command syntaxpathCliCommandCloseCannot call %1 when no database is set to be current. Specify current database with %2 command or pass database name to %3.Cannot call %1 when no database is set to be current. Specify current database with %2 command or pass database name to %3.Connection to database %1 closed.Connection to database %1 closed.No such database: %1. Use %2 to see list of known databases.No such database: %1. Use %2 to see list of known databases.closes given (or current) databasecloses given (or current) databaseCloses database connection. If the database was already closed, nothing happens. If <name> is provided, it should be name of the database to close (as printed by %1 command). The the <name> is not provided, then current working database is closed (see help for %2 for details).Closes database connection. If the database was already closed, nothing happens. If <name> is provided, it should be name of the database to close (as printed by %1 command). The the <name> is not provided, then current working database is closed (see help for %2 for details).nameCLI command syntaxnameCliCommandDbListNo current working database defined.No current working database defined.Databases:Databases:NameCLI db name columnNameOpenCLI connection state columnOpenClosedCLI connection state columnClosedConnectionCLI connection state columnConnectionDatabase file pathDatabase file pathprints list of registered databasesprints list of registered databasesPrints list of databases registered in the SQLiteStudio. Each database on the list can be in open or closed state and %1 tells you that. The current working database (aka default database) is also marked on the list with '*' at the start of its name. See help for %2 command to learn about the default database.Prints list of databases registered in the SQLiteStudio. Each database on the list can be in open or closed state and %1 tells you that. The current working database (aka default database) is also marked on the list with '*' at the start of its name. See help for %2 command to learn about the default database.CliCommandDescNo working database is set.
Call %1 command to set working database.
Call %2 to see list of all databases.No working database is set.
Call %1 command to set working database.
Call %2 to see list of all databases.Database is not open.Database is not open.Cannot find table named: %1Cannot find table named: %1shows details about the tableshows details about the tabletabletableTable: %1Table: %1Column nameColumn nameData typeData typeConstraintsConstraintsVirtual table: %1Virtual table: %1Construction arguments:Construction arguments:No construction arguments were passed for this virtual table.No construction arguments were passed for this virtual table.CliCommandDirlists directories and files in current working directorylists directories and files in current working directoryThis is very similar to 'dir' command known from Windows and 'ls' command from Unix systems.
You can pass <pattern> with wildcard characters to filter output.This is very similar to 'dir' command known from Windows and 'ls' command from Unix systems.
You can pass <pattern> with wildcard characters to filter output.patternpatternCliCommandExitquits the applicationquits the applicationQuits the application. Settings are stored in configuration file and will be restored on next startup.Quits the application. Settings are stored in configuration file and will be restored on next startup.CliCommandHelpshows this help messageshows this help messageUse %1 to learn about certain commands supported by the command line interface (CLI) of the SQLiteStudio.
To see list of supported commands, type %2 without any arguments.
When passing <command> name, you can skip special prefix character ('%3').
You can always execute any command with exactly single '--help' option to see help for that command. It's an alternative for typing: %1 <command>.Use %1 to learn about certain commands supported by the command line interface (CLI) of the SQLiteStudio.
To see list of supported commands, type %2 without any arguments.
When passing <command> name, you can skip special prefix character ('%3').
You can always execute any command with exactly single '--help' option to see help for that command. It's an alternative for typing: %1 <command>.commandCLI command syntaxcommandNo such command: %1No such command: %1Type '%1' for list of available commands.Type '%1' for list of available commands.Usage: %1%2Usage: %1%2Aliases: %1Aliases: %1CliCommandHistoryCurrent history limit is set to: %1Current history limit is set to: %1prints history or erases itprints history or erases itWhen no argument was passed, this command prints command line history. Every history entry is separated with a horizontal line, so multiline entries are easier to read.
When the -c or --clear option is passed, then the history gets erased.
When the -l or --limit option is passed, it sets the new history entries limit. It requires an additional argument saying how many entries do you want the history to be limited to.
Use -ql or --querylimit option to see the current limit value.When no argument was passed, this command prints command line history. Every history entry is separated with a horizontal line, so multiline entries are easier to read.
When the -c or --clear option is passed, then the history gets erased.
When the -l or --limit option is passed, it sets the new history entries limit. It requires an additional argument saying how many entries do you want the history to be limited to.
Use -ql or --querylimit option to see the current limit value.numbernumberConsole history erased.Console history erased.Invalid number: %1Invalid number: %1History limit set to %1History limit set to %1CliCommandModeCurrent results printing mode: %1Current results printing mode: %1Invalid results printing mode: %1Invalid results printing mode: %1New results printing mode: %1New results printing mode: %1tells or changes the query results formattells or changes the query results formatWhen called without argument, tells the current output format for a query results. When the <mode> is passed, the mode is changed to the given one. Supported modes are:
- CLASSIC - columns are separated by a comma, not aligned,
- FIXED - columns have equal and fixed width, they always fit into terminal window width, but the data in columns can be cut off,
- COLUMNS - like FIXED, but smarter (do not use with huge result sets, see details below),
- ROW - each column from the row is displayed in new line, so the full data is displayed.
The CLASSIC mode is recommended if you want to see all the data, but you don't want to waste lines for each column. Each row will display full data for every column, but this also means, that columns will not be aligned to each other in next rows. The CLASSIC mode also doesn't respect the width of your terminal (console) window, so if values in columns are wider than the window, the row will be continued in next lines.
The FIXED mode is recommended if you want a readable output and you don't care about long data values. Columns will be aligned, making the output a nice table. The width of columns is calculated from width of the console window and a number of columns.
The COLUMNS mode is similar to FIXED mode, except it tries to be smart and make columns with shorter values more thin, while columns with longer values get more space. First to shrink are columns with longest headers (so the header names are to be cut off as first), then columns with the longest values are shrinked, up to the moment when all columns fit into terminal window.
ATTENTION! The COLUMNS mode reads all the results from the query at once in order to evaluate column widths, therefore it is dangerous to use this mode when working with huge result sets. Keep in mind that this mode will load entire result set into memory.
The ROW mode is recommended if you need to see whole values and you don't expect many rows to be displayed, because this mode displays a line of output per each column, so you'll get 10 lines for single row with 10 columns, then if you have 10 of such rows, you will get 100 lines of output (+1 extra line per each row, to separate rows from each other).When called without argument, tells the current output format for a query results. When the <mode> is passed, the mode is changed to the given one. Supported modes are:
- CLASSIC - columns are separated by a comma, not aligned,
- FIXED - columns have equal and fixed width, they always fit into terminal window width, but the data in columns can be cut off,
- COLUMNS - like FIXED, but smarter (do not use with huge result sets, see details below),
- ROW - each column from the row is displayed in new line, so the full data is displayed.
The CLASSIC mode is recommended if you want to see all the data, but you don't want to waste lines for each column. Each row will display full data for every column, but this also means, that columns will not be aligned to each other in next rows. The CLASSIC mode also doesn't respect the width of your terminal (console) window, so if values in columns are wider than the window, the row will be continued in next lines.
The FIXED mode is recommended if you want a readable output and you don't care about long data values. Columns will be aligned, making the output a nice table. The width of columns is calculated from width of the console window and a number of columns.
The COLUMNS mode is similar to FIXED mode, except it tries to be smart and make columns with shorter values more thin, while columns with longer values get more space. First to shrink are columns with longest headers (so the header names are to be cut off as first), then columns with the longest values are shrinked, up to the moment when all columns fit into terminal window.
ATTENTION! The COLUMNS mode reads all the results from the query at once in order to evaluate column widths, therefore it is dangerous to use this mode when working with huge result sets. Keep in mind that this mode will load entire result set into memory.
The ROW mode is recommended if you need to see whole values and you don't expect many rows to be displayed, because this mode displays a line of output per each column, so you'll get 10 lines for single row with 10 columns, then if you have 10 of such rows, you will get 100 lines of output (+1 extra line per each row, to separate rows from each other).CliCommandNullValueCurrent NULL representation string: %1Current NULL representation string: %1tells or changes the NULL representation stringtells or changes the NULL representation stringIf no argument was passed, it tells what's the current NULL value representation (that is - what is printed in place of NULL values in query results). If the argument is given, then it's used as a new string to be used for NULL representation.If no argument was passed, it tells what's the current NULL value representation (that is - what is printed in place of NULL values in query results). If the argument is given, then it's used as a new string to be used for NULL representation.CliCommandOpenCannot call %1 when no database is set to be current. Specify current database with %2 command or pass database name to %3.Cannot call %1 when no database is set to be current. Specify current database with %2 command or pass database name to %3.Could not add database %1 to list.Could not add database %1 to list.File %1 doesn't exist in %2. Cannot open inexisting database with %3 command. To create a new database, use %4 command.File %1 doesn't exist in %2. Cannot open inexisting database with %3 command. To create a new database, use %4 command.Database %1 has been open and set as the current working database.Database %1 has been open and set as the current working database.opens database connectionopens database connectionOpens connection to the database. If no additional argument was passed, then the connection is open to the current default database (see help for %1 for details). However if an argument was passed, it can be either <name> of the registered database to open, or it can be <path> to the database file to open. In the second case, the <path> gets registered on the list with a generated name, but only for the period of current application session. After restarting application such database is not restored on the list.Opens connection to the database. If no additional argument was passed, then the connection is open to the current default database (see help for %1 for details). However if an argument was passed, it can be either <name> of the registered database to open, or it can be <path> to the database file to open. In the second case, the <path> gets registered on the list with a generated name, but only for the period of current application session. After restarting application such database is not restored on the list.nameCLI command syntaxnamepathCLI command syntaxpathCliCommandPwdprints the current working directoryprints the current working directoryThis is the same as 'pwd' command on Unix systems and 'cd' command without arguments on Windows. It prints current working directory. You can change the current working directory with %1 command and you can also list contents of the current working directory with %2 command.This is the same as 'pwd' command on Unix systems and 'cd' command without arguments on Windows. It prints current working directory. You can change the current working directory with %1 command and you can also list contents of the current working directory with %2 command.CliCommandRemoveNo such database: %1No such database: %1Database removed: %1Database removed: %1New current database set:New current database set:removes database from the listremoves database from the listRemoves <name> database from the list of registered databases. If the database was not on the list (see %1 command), then error message is printed and nothing more happens.Removes <name> database from the list of registered databases. If the database was not on the list (see %1 command), then error message is printed and nothing more happens.nameCLI command syntaxnameCliCommandSqlNo working database is set.
Call %1 command to set working database.
Call %2 to see list of all databases.No working database is set.
Call %1 command to set working database.
Call %2 to see list of all databases.Database is not open.Database is not open.executes SQL queryexecutes SQL queryThis command is executed every time you enter SQL query in command prompt. It executes the query on the current working database (see help for %1 for details). There's no sense in executing this command explicitly. Instead just type the SQL query in the command prompt, without any command prefixed.This command is executed every time you enter SQL query in command prompt. It executes the query on the current working database (see help for %1 for details). There's no sense in executing this command explicitly. Instead just type the SQL query in the command prompt, without any command prefixed.sqlCLI command syntaxsqlToo many columns to display in %1 mode.Too many columns to display in %1 mode.Row %1Row %1Query execution error: %1Query execution error: %1CliCommandTablesNo such database: %1. Use %2 to see list of known databases.No such database: %1. Use %2 to see list of known databases.Cannot call %1 when no database is set to be current. Specify current database with %2 command or pass database name to %3.Cannot call %1 when no database is set to be current. Specify current database with %2 command or pass database name to %3.Database %1 is closed.Database %1 is closed.DatabaseDatabaseTableTableprints list of tables in the databaseprints list of tables in the databasePrints list of tables in given <database> or in the current working database. Note, that the <database> should be the name of the registered database (see %1). The output list includes all tables from any other databases attached to the queried database.
When the -s option is given, then system tables are also listed.Prints list of tables in given <database> or in the current working database. Note, that the <database> should be the name of the registered database (see %1). The output list includes all tables from any other databases attached to the queried database.
When the -s option is given, then system tables are also listed.databaseCLI command syntaxdatabaseCliCommandTreeNo current working database is selected. Use %1 to define one and then run %2.No current working database is selected. Use %1 to define one and then run %2.TablesTablesViewsViewsColumnsColumnsIndexesIndexesTriggersTriggersprints all objects in the database as a treeprints all objects in the database as a treePrints all objects (tables, indexes, triggers and views) that are in the database as a tree. The tree is very similar to the one that you can see in GUI client of the SQLiteStudio.
When -c option is given, then also columns will be listed under each table.
When -s option is given, then also system objects will be printed (sqlite_* tables, autoincrement indexes, etc).
The database argument is optional and if provided, then only given database will be printed. This is not a registered database name, but instead it's an internal SQLite database name, like 'main', 'temp', or any attached database name. To print tree for other registered database, call %1 first to switch the working database, and then use %2 command.Prints all objects (tables, indexes, triggers and views) that are in the database as a tree. The tree is very similar to the one that you can see in GUI client of the SQLiteStudio.
When -c option is given, then also columns will be listed under each table.
When -s option is given, then also system objects will be printed (sqlite_* tables, autoincrement indexes, etc).
The database argument is optional and if provided, then only given database will be printed. This is not a registered database name, but instead it's an internal SQLite database name, like 'main', 'temp', or any attached database name. To print tree for other registered database, call %1 first to switch the working database, and then use %2 command.CliCommandUseNo current database selected.No current database selected.Current database: %1Current database: %1No such database: %1No such database: %1changes default working databasechanges default working databaseChanges current working database to <name>. If the <name> database is not registered in the application, then the error message is printed and no change is made.
What is current working database?
When you type a SQL query to be executed, it is executed on the default database, which is also known as the current working database. Most of database-related commands can also work using default database, if no database was provided in their arguments. The current database is always identified by command line prompt. The default database is always defined (unless there is no database on the list at all).
The default database can be selected in various ways:
- using %1 command,
- by passing database file name to the application startup parameters,
- by passing registered database name to the application startup parameters,
- by restoring previously selected default database from saved configuration,
- or when default database was not selected by any of the above, then first database from the registered databases list becomes the default one.Changes current working database to <name>. If the <name> database is not registered in the application, then the error message is printed and no change is made.
What is current working database?
When you type a SQL query to be executed, it is executed on the default database, which is also known as the current working database. Most of database-related commands can also work using default database, if no database was provided in their arguments. The current database is always identified by command line prompt. The default database is always defined (unless there is no database on the list at all).
The default database can be selected in various ways:
- using %1 command,
- by passing database file name to the application startup parameters,
- by passing registered database name to the application startup parameters,
- by restoring previously selected default database from saved configuration,
- or when default database was not selected by any of the above, then first database from the registered databases list becomes the default one.nameCLI command syntaxnameQObjectInsufficient number of arguments.Insufficient number of arguments.Too many arguments.Too many arguments.Invalid argument value: %1.
Expected one of: %2Invalid argument value: %1.
Expected one of: %2Unknown option: %1CLI command syntaxUnknown option: %1Option %1 requires an argument.CLI command syntaxOption %1 requires an argument.stringCLI command syntaxstringCommand line interface to SQLiteStudio, a SQLite manager.Command line interface to SQLiteStudio, a SQLite manager.Enables debug messages on standard error output.Enables debug messages on standard error output.Enables Lemon parser debug messages for SQL code assistant.Enables Lemon parser debug messages for SQL code assistant.Lists plugins installed in the SQLiteStudio and quits.Lists plugins installed in the SQLiteStudio and quits.Executes provided SQL file (including all rich features of SQLiteStudio's query executor) on the specified database file and quits. The database parameter becomes mandatory if this option is used.Executes provided SQL file (including all rich features of SQLiteStudio's query executor) on the specified database file and quits. The database parameter becomes mandatory if this option is used.SQL fileSQL fileCharacter encoding to use when reading SQL file (-e option). Use -cl to list available codecs. Defaults to %1.Character encoding to use when reading SQL file (-e option). Use -cl to list available codecs. Defaults to %1.codeccodecLists available codecs to be used with -c option and quits.Lists available codecs to be used with -c option and quits.When used together with -e option, the execution will not stop on an error, but rather continue until the end, ignoring errors.When used together with -e option, the execution will not stop on an error, but rather continue until the end, ignoring errors.filefileDatabase file to openDatabase file to openInvalid codec: %1. Use -cl option to list available codecs.Invalid codec: %1. Use -cl option to list available codecs.Database file argument is mandatory when executing SQL file.Database file argument is mandatory when executing SQL file.Could not open specified database for executing SQL file. You may try using -d option to find out more details.Could not open specified database for executing SQL file. You may try using -d option to find out more details.