stonebig / sqlite_bro

a graphic SQLite browser in 1 Python file

sqlite_bro : a graphic SQLite browser in 1 Python file

sqlite_bro is a tool to browse SQLite databases with any basic python installation.

Features

• Tabular browsing of a SQLite database
• Import/Export of .csv files with auto-detection
• Import/Export of .sql script
• Export of database creation .sql script
• Support of sql-embedded Python functions
• support supports command-line scripting if Python>=3.2 (see sqlite_bro -h), with or without Graphic User Interface
• Easy to distribute : 1 Python source file, Python and PyPy3 compatible
• Easy to start : just launch sqlite_bro
• Easy to learn : Welcome example, minimal interface
• Easy to teach : Character size, SQL + SQL result export on a click

Installation

You can install, upgrade, uninstall sqlite_bro.py with these commands:

$ apt-get install python3-tk # apt-get install python-tk if you are using python2
$ pip install sqlite_bro
$ pip install --upgrade sqlite_bro
$ pip uninstall sqlite_bro

or just launch latest version from IPython with %load https://raw.githubusercontent.com/stonebig/sqlite_bro/master/sqlite_bro/sqlite_bro.py or just copy the file 'sqlite_bro.py' to any pc and type 'python sqlite_bro.py'

Example usage

$ sqlite_bro

$ sqlite_bro -h

Screenshots

Links

• Fork me on GitHub

sqlite_bro's Issues

move to github actions

add .output , .print , .dump to command-line features

On the road to get more feature like sqlite3.exe:

• .output FILE = write all next commands to FILE
• .print = write after print to output
• .dump ?OBJECTS? = Render database content as SQL
• .read FILE = Read input from FILE
• .backup FILE
• .restore FILE

add a '.attach' command to allow attachement of database

ENH: bind F9 to run tab button

Dear stonebig,

Awesome tool! Thank you so much for developing this. Would you think a shortcut binding of F9 to "run tab" button will enhance the interface?

(The F9 key is from how Spyder runs selected code)

Shawn

connexion with odbc

using pyodbc or similar

principle:

• using sqlite_bro GUI over an odbc source (or sqlalchemy ?) :
  . connecting to "odbc" source, a source starting per odbc would be "odbc"
• using sqlite_bro to import from odbc to sqlite
• using sqlite_bro to export from sqlite to odbc.

interest:

• gui on anything in 1 file (if an odbc package)
• keep it simple

limit:

• not designed for performance
• not standard
• could be complex

on the ETL side

looking on what to improve to make it a better simple ETL for non-python experts:

• make it also work in truly non-gui situation
• .shell CMD ARGS... Run CMD ARGS... in a system shell ( .shell CMD/C whoami )
• more GUI menu option to match scripting progress

==> that is already ok on v0.12.1

replace 'utf-8-sig' per 'utf-8' as the default everywhere on Windows

we move utf-8 for automatic table export, as utf-8-sig practice is going away (yet somewhat better supported per sqlite = ignored at load)

it remains possible for some excel version (which will open in utf-8 only if utf-8-sig)

via .once 'toto.csv' --bom

see:
https://stackoverflow.com/questions/29468070/how-to-save-a-text-file-csv-with-utf-8-without-bom-encoding-in-vba-excel

https://sqlite.org/forum/forumpost/ed8f696a20

https://www.sqlite.org/src/info/d5b0def96ba6d90f

json output and input

allow direct database opening and scripting via command line

Contacts

Hey! Would love to talk to you about a project. Could you give me your email or email me at [email protected]?

waiting list for v 1.0

may better be:

• scripting mode: another round of consistency with sqlite.exe executable
• GUI mode:
  • another round on check that GUI is simple, obvious & coherent enough
  • is 'Welcome' tutorial simple enough ? (maybe a bit overkill on commits & rollbacks)

nice to have:

• support json output and input
• improve code quality
• more tests in continuous testing
• code coverage and download tags
• a .kernel thing https://twitter.com/jeremyphoward/status/1424990665746763781

add ".separator" and ".headers" shell instruction to complete the '.once' feature

.separator ; to have a ";" separator when doing '.once'
.separator ! to have a "!" separator when doing '.once'
.headers off to have no headers when doing '.once'
.headers on to have headers when doing '.once'