You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/index.md
+7-6
Original file line number
Diff line number
Diff line change
@@ -16,13 +16,14 @@ Cross-platform, zero dependencies, terminal based UI application for your Data B
16
16
17
17
## Overview
18
18
19
-
**dblab** is a fast and lightweight interactive terminal based UI application for PostgreSQL, MySQL and SQLite3, written in Go and works on OSX, Linux and Windows machines.
20
-
21
-
The main idea behind using Go for backend development is to utilize the ability of the compiler to produce zero-dependency binaries for multiple platforms.
22
-
23
-
dblab was created as an attempt to build a very simple and portable application to interact with local or remote PostgreSQL/MySQL/SQLite3databases.
19
+
dblab is a fast and lightweight interactive terminal based UI application for PostgreSQL, MySQL and SQLite3,
20
+
written in Go and works on OSX, Linux and Windows machines. Main idea behind using Go for backend development
21
+
is to utilize ability of the compiler to produce zero-dependency binaries for
22
+
multiple platforms. dblab was created as an attempt to build very simple and portable
23
+
application to work with local or remote PostgreSQL/MySQL/SQLite3/Oracle/SQL Server databases.
24
24
25
-
The key features are:
25
+
26
+
## Features
26
27
27
28
* Cross-platform support OSX/Linux/Windows 32/64-bit
28
29
* Simple installation (distributed as a single binary)
Use `dblab [command] --help` for more information about a command.
42
-
24
+
```
25
+
dblab is a terminal UI based interactive database client for Postgres, MySQL and SQLite3.
26
+
27
+
Usage:
28
+
dblab [flags]
29
+
dblab [command]
30
+
31
+
Available Commands:
32
+
help Help about any command
33
+
version The version of the project
34
+
35
+
Flags:
36
+
--cfg-name string Database config name section
37
+
--config Get the connection data from a config file (default locations are: current directory, $HOME/.dblab.yaml or $XDG_CONFIG_HOME/.dblab.yaml)
38
+
--db string Database name (optional)
39
+
--driver string Database driver
40
+
--encrypt string [strict|disable|false|true] data sent between client and server is encrypted or not
41
+
-h, --help help for dblab
42
+
--host string Server host name or IP
43
+
--limit uint Size of the result set from the table content query (should be greater than zero, otherwise the app will error out) (default 100)
44
+
--pass string Password for user
45
+
--port string Server port
46
+
--schema string Database schema (postgres only)
47
+
--socket string Path to a Unix socket file
48
+
--ssh-host string SSH Server Hostname/IP
49
+
--ssh-key string File with private key for SSH authentication
50
+
--ssh-key-pass string Supports connections with protected private keys with passphrase
51
+
--ssh-pass string SSH Password (Empty string for no password)
52
+
--ssh-port string SSH Port
53
+
--ssh-user string SSH User
54
+
--ssl string SSL mode
55
+
--ssl-verify string [enable|disable] or [true|false] enable ssl verify for the server
56
+
--sslcert string This parameter specifies the file name of the client SSL certificate, replacing the default ~/.postgresql/postgresql.crt
57
+
--sslkey string This parameter specifies the location for the secret key used for the client certificate. It can either specify a file name that will be used instead of the default ~/.postgresql/postgresql.key, or it can specify a key obtained from an external “engine”
58
+
--sslpassword string This parameter specifies the password for the secret key specified in sslkey
59
+
--sslrootcert string This parameter specifies the name of a file containing SSL certificate authority (CA) certificate(s) The default is ~/.postgresql/root.crt
60
+
--timeout string in seconds (default is 0 for no timeout), set to 0 for no timeout. Recommended to set to 0 and use context to manage query and connection timeouts
61
+
--trace-file string File name for trace log
62
+
--trust-server-certificate string [false|true] server certificate is checked or not
63
+
-u, --url string Database connection string
64
+
--user string Database user
65
+
-v, --version version for dblab
66
+
--wallet string Path for auto-login oracle wallet
67
+
68
+
Use "dblab [command] --help" for more information about a command.
69
+
```
43
70
44
71
## Navigation
45
72
@@ -89,7 +116,7 @@ Key | Description
89
116
90
117
You can start the app without passing flags or parameters, so then an interactive command prompt will ask for the connection details.
Now, it is possible to ensure SSL connections with `PostgreSQL` databases. SSL related parameters has been added, such as `--sslcert`, `--sslkey`, `--sslpassword`, `--sslrootcert`. More information on how to use such connection flags can be found [here](https://www.postgresql.org/docs/current/libpq-connect.html).
0 commit comments