NAME
dbinfo-sqlite - Get/extract information from SQLite database
VERSION
This document describes version 0.008 of dbinfo-sqlite (from Perl distribution App-dbinfo), released on 2020-05-06.
SYNOPSIS
List SQLite tables:
% dbinfo-sqlite list-tables mydata.db
List columns of a table:
% dbinfo-sqlite list-columns mydata.db mytable
% dbinfo-sqlite list-columns mydata.db mytable -l ;# show detail
Dump a table into various format:
% dbinfo-sqlite dump-table mydata.db mytable
DESCRIPTION
SUBCOMMANDS
dump-table
Dump SQLite table into various formats.
list-columns
List columns of a SQLite database table.
list-indexes
List SQLite table indexes.
list-tables
List tables in the SQLite database.
OPTIONS
*
marks required options.
Common options
- --config-path=s, -c
-
Set path to configuration file.
- --config-profile=s, -P
-
Set configuration profile to use.
- --dbpath=s
- --debug
-
Shortcut for --log-level=debug.
- --format=s
-
Choose output format, e.g. json, text.
Default value:
undef
- --help, -h, -?
-
Display help message and exit.
- --json
-
Set output format to json.
- --log-level=s
-
Set log level.
- --naked-res
-
When outputing as JSON, strip result envelope.
Default value:
0
By default, when outputing as JSON, the full enveloped result is returned, e.g.:
[200,"OK",[1,2,3],{"func.extra"=>4}]
The reason is so you can get the status (1st element), status message (2nd element) as well as result metadata/extra result (4th element) instead of just the result (3rd element). However, sometimes you want just the result, e.g. when you want to pipe the result for more post-processing. In this case you can use `--naked-res` so you just get:
[1,2,3]
- --no-config, -C
-
Do not use any configuration file.
- --no-env
-
Do not read environment for default options.
- --page-result
-
Filter output through a pager.
- --quiet
-
Shortcut for --log-level=error.
- --subcommands
-
List available subcommands.
- --trace
-
Shortcut for --log-level=trace.
- --verbose
-
Shortcut for --log-level=info.
- --version, -v
-
Display program's version and exit.
Options for subcommand dump-table
- --array
-
Shortcut for --row-format=array.
See
--row-format
. - --exclude-column=s@
-
Can be specified multiple times.
- --exclude-columns-json=s
-
See
--exclude-column
. - --include-column=s@
-
Can be specified multiple times.
- --include-columns-json=s
-
See
--include-column
. - --limit-number=s, -n
- --limit-offset=s, -o
- --row-format=s
-
Default value:
"hash"
Valid values:
["array","hash"]
- --table=s*
-
Table name.
- --where=s@, -w
-
Add WHERE clause.
Can be specified multiple times.
- --wheres-json=s
-
Add WHERE clause (JSON-encoded).
See
--where
. - -a
-
Shortcut for --row-format=array.
See
--row-format
.
Options for subcommand list-columns
Options for subcommand list-indexes
COMPLETION
This script has shell tab completion capability with support for several shells.
bash
To activate bash completion for this script, put:
complete -C dbinfo-sqlite dbinfo-sqlite
in your bash startup (e.g. ~/.bashrc). Your next shell session will then recognize tab completion for the command. Or, you can also directly execute the line above in your shell to activate immediately.
It is recommended, however, that you install modules using cpanm-shcompgen which can activate shell completion for scripts immediately.
tcsh
To activate tcsh completion for this script, put:
complete dbinfo-sqlite 'p/*/`dbinfo-sqlite`/'
in your tcsh startup (e.g. ~/.tcshrc). Your next shell session will then recognize tab completion for the command. Or, you can also directly execute the line above in your shell to activate immediately.
It is also recommended to install shcompgen (see above).
other shells
For fish and zsh, install shcompgen as described above.
CONFIGURATION FILE
This script can read configuration files. Configuration files are in the format of IOD, which is basically INI with some extra features.
By default, these names are searched for configuration filenames (can be changed using --config-path
): ~/.config/dbinfo-sqlite.conf, ~/dbinfo-sqlite.conf, or /etc/dbinfo-sqlite.conf.
All found files will be read and merged.
To disable searching for configuration files, pass --no-config
.
To put configuration for a certain subcommand only, use a section name like [subcommand=NAME]
or [SOMESECTION subcommand=NAME]
.
You can put multiple profiles in a single file by using section names like [profile=SOMENAME]
or [SOMESECTION profile=SOMENAME]
or [subcommand=SUBCOMMAND_NAME profile=SOMENAME]
or [SOMESECTION subcommand=SUBCOMMAND_NAME profile=SOMENAME]
. Those sections will only be read if you specify the matching --config-profile SOMENAME
.
You can also put configuration for multiple programs inside a single file, and use filter program=NAME
in section names, e.g. [program=NAME ...]
or [SOMESECTION program=NAME]
. The section will then only be used when the reading program matches.
Finally, you can filter a section by environment variable using the filter env=CONDITION
in section names. For example if you only want a section to be read if a certain environment variable is true: [env=SOMEVAR ...]
or [SOMESECTION env=SOMEVAR ...]
. If you only want a section to be read when the value of an environment variable has value equals something: [env=HOSTNAME=blink ...]
or [SOMESECTION env=HOSTNAME=blink ...]
. If you only want a section to be read when the value of an environment variable does not equal something: [env=HOSTNAME!=blink ...]
or [SOMESECTION env=HOSTNAME!=blink ...]
. If you only want a section to be read when an environment variable contains something: [env=HOSTNAME*=server ...]
or [SOMESECTION env=HOSTNAME*=server ...]
. Note that currently due to simplistic parsing, there must not be any whitespace in the value being compared because it marks the beginning of a new section filter or section name.
List of available configuration parameters:
Common for all subcommands
dbpath (see --dbpath)
format (see --format)
log_level (see --log-level)
naked_res (see --naked-res)
Configuration for subcommand dump-table
exclude_columns (see --exclude-column)
include_columns (see --include-column)
limit_number (see --limit-number)
limit_offset (see --limit-offset)
row_format (see --row-format)
table (see --table)
wheres (see --where)
Configuration for subcommand list-columns
detail (see --detail)
table (see --table)
Configuration for subcommand list-indexes
table (see --table)
Configuration for subcommand list-tables
ENVIRONMENT
DBINFO_SQLITE_OPT => str
Specify additional command-line options.
FILES
~/.config/dbinfo-sqlite.conf
~/dbinfo-sqlite.conf
/etc/dbinfo-sqlite.conf
HOMEPAGE
Please visit the project's homepage at https://metacpan.org/release/App-dbinfo.
SOURCE
Source repository is at https://github.com/perlancar/perl-App-dbinfo.
BUGS
Please report any bugs or feature requests on the bugtracker website https://rt.cpan.org/Public/Dist/Display.html?Name=App-dbinfo
When submitting a bug or request, please include a test-file or a patch to an existing test-file that illustrates the bug or desired feature.
SEE ALSO
dbinfo-sqlite, ...
mysqlinfo from App::mysqlinfo
AUTHOR
perlancar <perlancar@cpan.org>
COPYRIGHT AND LICENSE
This software is copyright (c) 2020, 2019, 2018, 2017 by perlancar@cpan.org.
This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.