sqlit-tui 1.0.2__tar.gz → 1.1__tar.gz

{sqlit_tui-1.0.2 → sqlit_tui-1.1}/.github/workflows/release.yml

@@ -101,47 +101,48 @@ jobs:
             echo "VERSION=${GITHUB_REF#refs/tags/v}" >> $GITHUB_OUTPUT
           fi
 
-      - name: Setup SSH for AUR
+      - name: Wait for PyPI and get checksum
+        id: pypi
         run: |
-          mkdir -p ~/.ssh
-          # Decode base64-encoded SSH key (encode with: base64 -w 0 < ~/.ssh/aur_key)
-          echo "${{ secrets.AUR_SSH_KEY }}" | base64 -d > ~/.ssh/aur
-          chmod 600 ~/.ssh/aur
-          echo "Host aur.archlinux.org" >> ~/.ssh/config
-          echo "  IdentityFile ~/.ssh/aur" >> ~/.ssh/config
-          echo "  User aur" >> ~/.ssh/config
-          ssh-keyscan aur.archlinux.org >> ~/.ssh/known_hosts
-
-      - name: Clone AUR repo
-        run: git clone ssh://aur@aur.archlinux.org/python-sqlit-tui.git aur-repo
+          VERSION=${{ steps.version.outputs.VERSION }}
+          URL="https://files.pythonhosted.org/packages/source/s/sqlit-tui/sqlit_tui-${VERSION}.tar.gz"
+
+          echo "Waiting for package to be available on PyPI..."
+          for i in {1..20}; do
+            HTTP_CODE=$(curl -sI -o /dev/null -w "%{http_code}" "$URL")
+            if [ "$HTTP_CODE" = "200" ]; then
+              echo "Package available on PyPI (attempt $i)"
+              break
+            fi
+            echo "Waiting for PyPI... attempt $i (got HTTP $HTTP_CODE)"
+            sleep 30
+          done
+
+          # Download and compute checksum
+          curl -sL "$URL" -o /tmp/pkg.tar.gz
+          CHECKSUM=$(sha256sum /tmp/pkg.tar.gz | cut -d' ' -f1)
+          echo "CHECKSUM=${CHECKSUM}" >> $GITHUB_OUTPUT
+          echo "Checksum: ${CHECKSUM}"
 
       - name: Update PKGBUILD
         run: |
-          cd aur-repo
           VERSION=${{ steps.version.outputs.VERSION }}
+          CHECKSUM=${{ steps.pypi.outputs.CHECKSUM }}
 
-          # Wait for PyPI to have the package available
-          sleep 30
-
-          # Download new tarball and get checksum
-          curl -sL "https://files.pythonhosted.org/packages/source/s/sqlit-tui/sqlit_tui-${VERSION}.tar.gz" -o /tmp/pkg.tar.gz
-          CHECKSUM=$(sha256sum /tmp/pkg.tar.gz | cut -d' ' -f1)
-
-          # Update version and checksum in PKGBUILD
+          cd aur
           sed -i "s/^pkgver=.*/pkgver=${VERSION}/" PKGBUILD
           sed -i "s/^pkgrel=.*/pkgrel=1/" PKGBUILD
           sed -i "s/^sha256sums=.*/sha256sums=('${CHECKSUM}')/" PKGBUILD
 
-          # Update .SRCINFO
-          sed -i "s/pkgver = .*/pkgver = ${VERSION}/" .SRCINFO
-          sed -i "s/sqlit_tui-[0-9.]*/sqlit_tui-${VERSION}/g" .SRCINFO
-          sed -i "s/sha256sums = .*/sha256sums = ${CHECKSUM}/" .SRCINFO
+          echo "Updated PKGBUILD:"
+          cat PKGBUILD
 
-      - name: Push to AUR
-        run: |
-          cd aur-repo
-          git config user.email "peter.w.adams96@gmail.com"
-          git config user.name "Peter"
-          git add PKGBUILD .SRCINFO
-          git diff --staged --quiet || git commit -m "Update to v${{ steps.version.outputs.VERSION }}"
-          git push
+      - name: Publish to AUR
+        uses: KSXGitHub/github-actions-deploy-aur@v3.0.1
+        with:
+          pkgname: python-sqlit-tui
+          pkgbuild: ./aur/PKGBUILD
+          commit_username: Peter
+          commit_email: peter.w.adams96@gmail.com
+          ssh_private_key: ${{ secrets.AUR_SSH_PRIVATE_KEY }}
+          commit_message: "Update to v${{ steps.version.outputs.VERSION }}"

{sqlit_tui-1.0.2 → sqlit_tui-1.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: sqlit-tui
-Version: 1.0.2
+Version: 1.1
 Summary: A terminal UI for SQL Server, PostgreSQL, MySQL, SQLite, and Oracle
 Project-URL: Homepage, https://github.com/Maxteabag/sqlit
 Project-URL: Repository, https://github.com/Maxteabag/sqlit
@@ -21,41 +21,45 @@ Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
 Classifier: Topic :: Database
 Requires-Python: >=3.10
+Requires-Dist: docker>=7.0.0
 Requires-Dist: keyring>=24.0.0
 Requires-Dist: pyperclip>=1.8.2
+Requires-Dist: textual-fastdatatable>=0.14.0
 Requires-Dist: textual[syntax]>=6.10.0
 Provides-Extra: all
-Requires-Dist: duckdb>=0.9.0; extra == 'all'
+Requires-Dist: duckdb>=1.1.0; extra == 'all'
 Requires-Dist: libsql-client>=0.1.0; extra == 'all'
 Requires-Dist: mariadb>=1.1.0; extra == 'all'
-Requires-Dist: mysql-connector-python>=8.0.0; extra == 'all'
+Requires-Dist: mysql-connector-python>=9.1.0; extra == 'all'
 Requires-Dist: oracledb>=2.0.0; extra == 'all'
 Requires-Dist: paramiko<4.0.0,>=2.0.0; extra == 'all'
 Requires-Dist: psycopg2-binary>=2.9.0; extra == 'all'
 Requires-Dist: pyodbc>=5.0.0; extra == 'all'
-Requires-Dist: requests>=2.0.0; extra == 'all'
+Requires-Dist: requests>=2.32.4; extra == 'all'
 Requires-Dist: sshtunnel>=0.4.0; extra == 'all'
 Provides-Extra: cockroachdb
 Requires-Dist: psycopg2-binary>=2.9.0; extra == 'cockroachdb'
 Provides-Extra: d1
-Requires-Dist: requests>=2.0.0; extra == 'd1'
+Requires-Dist: requests>=2.32.4; extra == 'd1'
 Provides-Extra: dev
 Requires-Dist: build; extra == 'dev'
+Requires-Dist: faker>=28.0; extra == 'dev'
 Requires-Dist: mypy>=1.0; extra == 'dev'
 Requires-Dist: pre-commit>=3.0; extra == 'dev'
 Requires-Dist: pytest-asyncio>=0.23.0; extra == 'dev'
+Requires-Dist: pytest-benchmark>=4.0; extra == 'dev'
 Requires-Dist: pytest-cov>=4.0; extra == 'dev'
 Requires-Dist: pytest-timeout>=2.0; extra == 'dev'
 Requires-Dist: pytest>=7.0; extra == 'dev'
 Requires-Dist: ruff>=0.8.0; extra == 'dev'
 Provides-Extra: duckdb
-Requires-Dist: duckdb>=0.9.0; extra == 'duckdb'
+Requires-Dist: duckdb>=1.1.0; extra == 'duckdb'
 Provides-Extra: mariadb
 Requires-Dist: mariadb>=1.1.0; extra == 'mariadb'
 Provides-Extra: mssql
 Requires-Dist: pyodbc>=5.0.0; extra == 'mssql'
 Provides-Extra: mysql
-Requires-Dist: mysql-connector-python>=8.0.0; extra == 'mysql'
+Requires-Dist: mysql-connector-python>=9.1.0; extra == 'mysql'
 Provides-Extra: oracle
 Requires-Dist: oracledb>=2.0.0; extra == 'oracle'
 Provides-Extra: postgres
@@ -86,6 +90,8 @@ A lightweight TUI for people who just want to run some queries fast.
 
 ### Query History
 ![Query History](demos/demo-history.gif)
+**Filter results**
+![Filter results](demos/demo-filter/demo-filter.gif)
 
 
 ## Features
@@ -93,11 +99,14 @@ A lightweight TUI for people who just want to run some queries fast.
 - **Connection manager UI** - Save connections, switch between databases without CLI args
 - **Just run `sqlit`** - No CLI config needed, pick a connection and go
 - **Multi-database out of the box** - SQL Server, PostgreSQL, MySQL, SQLite, MariaDB, Oracle, DuckDB, CockroachDB, Supabase, Turso - no adapters to install
+- Connect directly to database docker container
 - **SSH tunnels built-in** - Connect to remote databases securely with password or key auth
 - **Vim-style editing** - Modal editing for terminal purists
 - **Query history** - Automatically saves queries per connection, searchable and sortable
+- Filter results
 - Context-aware help (no need to memorize keybindings)
 - Browse databases, tables, views, and stored procedures
+- Indexes, Triggers and Sequences
 - SQL autocomplete for tables, columns, and procedures
 - Multiple auth methods (Windows, SQL Server, Entra ID)
 - CLI mode for scripting and AI agents
@@ -177,6 +186,14 @@ sqlit connections add postgresql --name "RemoteDB" --server "db-host" --username
 # Temporary (not saved) connection
 sqlit connect sqlite --file-path "/path/to/database.db"
 
+# Connect via URL - scheme determines database type (postgresql://, mysql://, sqlite://, etc.)
+sqlit postgresql://user:pass@localhost:5432/mydb
+sqlit mysql://root@localhost/testdb
+sqlit sqlite:///path/to/database.db
+
+# Save a connection via URL
+sqlit connections add --url dbtype://user:pass@host/db --name "MyDB"
+
 # Provider-specific CLI help
 sqlit connect -h
 sqlit connect supabase -h
@@ -282,6 +299,84 @@ SSH tunnel functionality requires additional dependencies. Install with the `ssh
 
 If you try to create an SSH connection without these dependencies, sqlit will detect this and show you the exact command to install them for your environment.
 
+### Vision
+
+The core purpose of this application is to read Read&Write to a SQL database.
+The core elements to achieve this purpose is: CEQR:
+
+- C: Connecting
+- E: Exploring
+- Q: Querying
+- R: Viewing results
+
+Connecting: Connecting to a server
+Exploring: Understanding the structure and content of the databases
+Querying: Executing SQL queries
+D: Viewing the results of SQL queries
+
+Additionally, we have requirements 'EAFF':
+
+- E: Easy
+- A: Aesthetically pleasing
+- F: Fun
+- F: Fast
+
+If an idea or feature does *not* achieve any of the 'CBQV' elements adhering to all of the 'EAFF' requirements. It does not belong to sqlit.
+
+**[E]asy:**
+Sqlit should not require any external documentation at all. It must prioritize intuitiveness above all.
+
+**[A]esthetically pleasing:**
+Sqlit should not render one unnecessary pixel. It should prioritize beauty above anything. Minimalism over bloat.
+
+**Fun:**
+Sqlit aims make fulfilling its core purpose be an enjoyable experience for the user, even a source of pleasure.
+
+**Fast:**
+Sqlit aims to fulfill its core purpose for the user, with intention to giving the user the results they want with as few actions as possible.
+
+Essentially, sqlit aims to do CRUD on SQL really well.
+
+This implies this tool is more suited for developer's daily use than an database administrator.
+Every feature in sqlit should have a target audience in which they will use it every time they use sqlit.
+If nobody is going to a feature every day. It does not belong to sqlit.
+E.g.
+
+1) advanced query performance debugging -> rarely used -> does not belong in sqlit
+2) edit cell key-binding -> a audience who will use this every day -> belongs to sqlit
+
+**On complexity:**
+Minimalism: sqlit aims to abstract away as much complexity as possible from the user, while giving them enough control to achieve CBQV. sqlit should never do anything under the hood that the user might have interest in understanding. Universal state problems deem for magical fixes. Conditional state problems, explicit user awareness. User should never ask "wait, how did it know?" "why is this here?" "why did it work then, but not now?"
+
+Voluntary advanced usage: Anything beyond most essentials to achieve CEQR should be voluntary to be exposed to. Minimal cogntive overhead. Always assume by default our user just wants to perform CRUD with SQL.
+
+The idea is the user is exposed to an interface that's minimalistic and easy, but if they want to become 'power users' they may dig into command menu or see help and memorize.
+
+Advances features should not be advertised on the main tool bar or anywhere else where the user has no say in whether it's rendered, as they take up space and distract from the most essential features for crud.
+
+One state: There should be no settings or preferences with important exception of interface (aesthetics, keyboard bindings). No settings to enable or disable features for conditional behaviour. Do not include a feature that a user finds annoying. Settings to disable a feature is a symptom of this. Anything beyond essential must be sought after if needed, not disabled if unwanted.
+
+**Keybindings philosophy:**
+To make sqlit as fast' as possible, sqlit has a large focus on keybindings.
+To make sqlit as 'easy' as possible, all necessary keybindings to do 'CEQR' well, must be visible at all times.
+To make sqlit as 'aesthetically pleasing' any keybinding not strictly necessary to perform 'CEQR' in a 'easy' and 'fast' way will be hidden behind help <?> or command menu <space>
+Keybindings will favour 'vim' traditions as the core audience is developers who enjoy working in terminals.
+We shy away from ^+ commands and will only use them where it is not natural to have a "insert/normal" mode and where input is crucial. (Typical is pop up modals)
+
+**Ideal:**
+It should be easy to use for someone who just started using sqlit.
+sqlit should provide fun and a feeling of mastery and satisfaction for those who want to achieve it, by becoming a sql-manipulating wizard with creative keybinding combos.
+
+**Designing keybindings decision hierarchy:**
+
+1. Intuitive to learn
+2. Harmony (we should think about which keybindings are used in sequence, in typical to flow and maximize user mastery satisfaction and opportunity to combine them fast)
+3. Traditions (vim, specifically)
+
+**Example:**
+<e> = explorer pane, <q> = query pane, <r> = results pane.
+Rationale: E;Q;R satisfies both intuitiveness (each binding is the first letter of the pane), harmony (proximity: qwerty speaks for itself)
+
 ## License
 
 MIT

{sqlit_tui-1.0.2 → sqlit_tui-1.1}/README.md

@@ -12,6 +12,8 @@ A lightweight TUI for people who just want to run some queries fast.
 
 ### Query History
 ![Query History](demos/demo-history.gif)
+**Filter results**
+![Filter results](demos/demo-filter/demo-filter.gif)
 
 
 ## Features
@@ -19,11 +21,14 @@ A lightweight TUI for people who just want to run some queries fast.
 - **Connection manager UI** - Save connections, switch between databases without CLI args
 - **Just run `sqlit`** - No CLI config needed, pick a connection and go
 - **Multi-database out of the box** - SQL Server, PostgreSQL, MySQL, SQLite, MariaDB, Oracle, DuckDB, CockroachDB, Supabase, Turso - no adapters to install
+- Connect directly to database docker container
 - **SSH tunnels built-in** - Connect to remote databases securely with password or key auth
 - **Vim-style editing** - Modal editing for terminal purists
 - **Query history** - Automatically saves queries per connection, searchable and sortable
+- Filter results
 - Context-aware help (no need to memorize keybindings)
 - Browse databases, tables, views, and stored procedures
+- Indexes, Triggers and Sequences
 - SQL autocomplete for tables, columns, and procedures
 - Multiple auth methods (Windows, SQL Server, Entra ID)
 - CLI mode for scripting and AI agents
@@ -103,6 +108,14 @@ sqlit connections add postgresql --name "RemoteDB" --server "db-host" --username
 # Temporary (not saved) connection
 sqlit connect sqlite --file-path "/path/to/database.db"
 
+# Connect via URL - scheme determines database type (postgresql://, mysql://, sqlite://, etc.)
+sqlit postgresql://user:pass@localhost:5432/mydb
+sqlit mysql://root@localhost/testdb
+sqlit sqlite:///path/to/database.db
+
+# Save a connection via URL
+sqlit connections add --url dbtype://user:pass@host/db --name "MyDB"
+
 # Provider-specific CLI help
 sqlit connect -h
 sqlit connect supabase -h
@@ -208,6 +221,84 @@ SSH tunnel functionality requires additional dependencies. Install with the `ssh
 
 If you try to create an SSH connection without these dependencies, sqlit will detect this and show you the exact command to install them for your environment.
 
+### Vision
+
+The core purpose of this application is to read Read&Write to a SQL database.
+The core elements to achieve this purpose is: CEQR:
+
+- C: Connecting
+- E: Exploring
+- Q: Querying
+- R: Viewing results
+
+Connecting: Connecting to a server
+Exploring: Understanding the structure and content of the databases
+Querying: Executing SQL queries
+D: Viewing the results of SQL queries
+
+Additionally, we have requirements 'EAFF':
+
+- E: Easy
+- A: Aesthetically pleasing
+- F: Fun
+- F: Fast
+
+If an idea or feature does *not* achieve any of the 'CBQV' elements adhering to all of the 'EAFF' requirements. It does not belong to sqlit.
+
+**[E]asy:**
+Sqlit should not require any external documentation at all. It must prioritize intuitiveness above all.
+
+**[A]esthetically pleasing:**
+Sqlit should not render one unnecessary pixel. It should prioritize beauty above anything. Minimalism over bloat.
+
+**Fun:**
+Sqlit aims make fulfilling its core purpose be an enjoyable experience for the user, even a source of pleasure.
+
+**Fast:**
+Sqlit aims to fulfill its core purpose for the user, with intention to giving the user the results they want with as few actions as possible.
+
+Essentially, sqlit aims to do CRUD on SQL really well.
+
+This implies this tool is more suited for developer's daily use than an database administrator.
+Every feature in sqlit should have a target audience in which they will use it every time they use sqlit.
+If nobody is going to a feature every day. It does not belong to sqlit.
+E.g.
+
+1) advanced query performance debugging -> rarely used -> does not belong in sqlit
+2) edit cell key-binding -> a audience who will use this every day -> belongs to sqlit
+
+**On complexity:**
+Minimalism: sqlit aims to abstract away as much complexity as possible from the user, while giving them enough control to achieve CBQV. sqlit should never do anything under the hood that the user might have interest in understanding. Universal state problems deem for magical fixes. Conditional state problems, explicit user awareness. User should never ask "wait, how did it know?" "why is this here?" "why did it work then, but not now?"
+
+Voluntary advanced usage: Anything beyond most essentials to achieve CEQR should be voluntary to be exposed to. Minimal cogntive overhead. Always assume by default our user just wants to perform CRUD with SQL.
+
+The idea is the user is exposed to an interface that's minimalistic and easy, but if they want to become 'power users' they may dig into command menu or see help and memorize.
+
+Advances features should not be advertised on the main tool bar or anywhere else where the user has no say in whether it's rendered, as they take up space and distract from the most essential features for crud.
+
+One state: There should be no settings or preferences with important exception of interface (aesthetics, keyboard bindings). No settings to enable or disable features for conditional behaviour. Do not include a feature that a user finds annoying. Settings to disable a feature is a symptom of this. Anything beyond essential must be sought after if needed, not disabled if unwanted.
+
+**Keybindings philosophy:**
+To make sqlit as fast' as possible, sqlit has a large focus on keybindings.
+To make sqlit as 'easy' as possible, all necessary keybindings to do 'CEQR' well, must be visible at all times.
+To make sqlit as 'aesthetically pleasing' any keybinding not strictly necessary to perform 'CEQR' in a 'easy' and 'fast' way will be hidden behind help <?> or command menu <space>
+Keybindings will favour 'vim' traditions as the core audience is developers who enjoy working in terminals.
+We shy away from ^+ commands and will only use them where it is not natural to have a "insert/normal" mode and where input is crucial. (Typical is pop up modals)
+
+**Ideal:**
+It should be easy to use for someone who just started using sqlit.
+sqlit should provide fun and a feeling of mastery and satisfaction for those who want to achieve it, by becoming a sql-manipulating wizard with creative keybinding combos.
+
+**Designing keybindings decision hierarchy:**
+
+1. Intuitive to learn
+2. Harmony (we should think about which keybindings are used in sequence, in typical to flow and maximize user mastery satisfaction and opportunity to combine them fast)
+3. Traditions (vim, specifically)
+
+**Example:**
+<e> = explorer pane, <q> = query pane, <r> = results pane.
+Rationale: E;Q;R satisfies both intuitiveness (each binding is the first letter of the pane), harmony (proximity: qwerty speaks for itself)
+
 ## License
 
 MIT

sqlit_tui-1.1/demos/d1-demo.json

@@ -0,0 +1,185 @@
+{
+  "mock": {
+    "enabled": true,
+    "profile": "d1-demo",
+    "connections": [],
+    "adapters": {
+      "d1": {
+        "name": "Cloudflare D1",
+        "default_schema": "main",
+        "connect": {
+          "result": "success"
+        },
+        "schemas": {
+          "main": {
+            "tables": {
+              "users": {
+                "columns": [
+                  {
+                    "name": "id",
+                    "type": "INTEGER"
+                  },
+                  {
+                    "name": "email",
+                    "type": "TEXT"
+                  },
+                  {
+                    "name": "name",
+                    "type": "TEXT"
+                  },
+                  {
+                    "name": "created_at",
+                    "type": "TEXT"
+                  }
+                ],
+                "rows": [
+                  [
+                    1,
+                    "alice@example.com",
+                    "Alice Chen",
+                    "2024-11-01"
+                  ],
+                  [
+                    2,
+                    "bob@example.com",
+                    "Bob Smith",
+                    "2024-11-05"
+                  ],
+                  [
+                    3,
+                    "carol@example.com",
+                    "Carol Davis",
+                    "2024-11-10"
+                  ]
+                ]
+              },
+              "posts": {
+                "columns": [
+                  {
+                    "name": "id",
+                    "type": "INTEGER"
+                  },
+                  {
+                    "name": "user_id",
+                    "type": "INTEGER"
+                  },
+                  {
+                    "name": "title",
+                    "type": "TEXT"
+                  },
+                  {
+                    "name": "published",
+                    "type": "INTEGER"
+                  }
+                ],
+                "rows": [
+                  [
+                    1,
+                    1,
+                    "Getting Started with D1",
+                    1
+                  ],
+                  [
+                    2,
+                    1,
+                    "Edge Computing Basics",
+                    1
+                  ],
+                  [
+                    3,
+                    2,
+                    "Workers and D1",
+                    0
+                  ],
+                  [
+                    4,
+                    3,
+                    "SQLite at the Edge",
+                    1
+                  ]
+                ]
+              },
+              "analytics": {
+                "columns": [
+                  {
+                    "name": "id",
+                    "type": "INTEGER"
+                  },
+                  {
+                    "name": "post_id",
+                    "type": "INTEGER"
+                  },
+                  {
+                    "name": "views",
+                    "type": "INTEGER"
+                  },
+                  {
+                    "name": "date",
+                    "type": "TEXT"
+                  }
+                ],
+                "rows": [
+                  [
+                    1,
+                    1,
+                    1250,
+                    "2024-12-01"
+                  ],
+                  [
+                    2,
+                    2,
+                    890,
+                    "2024-12-01"
+                  ],
+                  [
+                    3,
+                    4,
+                    445,
+                    "2024-12-01"
+                  ],
+                  [
+                    4,
+                    1,
+                    320,
+                    "2024-12-02"
+                  ]
+                ]
+              }
+            }
+          }
+        },
+        "query_results": {
+          "join": {
+            "columns": [
+              "author",
+              "title",
+              "total_views"
+            ],
+            "rows": [
+              [
+                "Alice Chen",
+                "Getting Started with D1",
+                1570
+              ],
+              [
+                "Alice Chen",
+                "Edge Computing Basics",
+                890
+              ],
+              [
+                "Carol Davis",
+                "SQLite at the Edge",
+                445
+              ]
+            ]
+          }
+        }
+      }
+    }
+  },
+  "theme": "sqlit",
+  "expanded_nodes": [
+    "conn:My D1 Database",
+    "conn:My D1 Database/folder:tables"
+  ]
+}

{sqlit_tui-1.0.2 → sqlit_tui-1.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "sqlit-tui"
-version = "1.0.2"
+version = "1.1"
 description = "A terminal UI for SQL Server, PostgreSQL, MySQL, SQLite, and Oracle"
 readme = "README.md"
 license = "MIT"
@@ -28,19 +28,21 @@ classifiers = [
 ]
 dependencies = [
     "textual[syntax]>=6.10.0",
+    "textual-fastdatatable>=0.14.0",
     "pyperclip>=1.8.2",
     "keyring>=24.0.0",
+    "docker>=7.0.0",  # Docker container auto-detection (lazy loaded)
 ]
 
 [project.optional-dependencies]
 all = [
     "psycopg2-binary>=2.9.0",
     "pyodbc>=5.0.0",
-    "mysql-connector-python>=8.0.0",
+    "mysql-connector-python>=9.1.0",  # min avoids known CVEs
     "mariadb>=1.1.0",
     "oracledb>=2.0.0",
-    "duckdb>=0.9.0",
-    "requests>=2.0.0",
+    "duckdb>=1.1.0",  # min avoids known CVEs
+    "requests>=2.32.4",  # min avoids known CVEs
     "libsql-client>=0.1.0",
     "sshtunnel>=0.4.0",
     "paramiko>=2.0.0,<4.0.0",
@@ -48,11 +50,11 @@ all = [
 postgres = ["psycopg2-binary>=2.9.0"]
 cockroachdb = ["psycopg2-binary>=2.9.0"]
 mssql = ["pyodbc>=5.0.0"]
-mysql = ["mysql-connector-python>=8.0.0"]
+mysql = ["mysql-connector-python>=9.1.0"]  # min avoids known CVEs
 mariadb = ["mariadb>=1.1.0"]
 oracle = ["oracledb>=2.0.0"]
-duckdb = ["duckdb>=0.9.0"]
-d1 = ["requests>=2.0.0"]
+duckdb = ["duckdb>=1.1.0"]  # min avoids known CVEs
+d1 = ["requests>=2.32.4"]  # min avoids known CVEs
 turso = ["libsql-client>=0.1.0"]
 ssh = [
     "sshtunnel>=0.4.0",
@@ -69,6 +71,8 @@ dev = [
     "pytest-timeout>=2.0",
     "pytest-asyncio>=0.23.0",
     "pytest-cov>=4.0",
+    "pytest-benchmark>=4.0",
+    "Faker>=28.0",
     "build",
     "ruff>=0.8.0",
     "mypy>=1.0",
@@ -107,6 +111,7 @@ markers = [
     "mysql: MySQL database tests",
     "oracle: Oracle database tests",
     "asyncio: async tests",
+    "integration: integration tests (may require external services)",
 ]
 
 [tool.coverage.run]
@@ -138,7 +143,11 @@ module = [
     "oracledb",
     "duckdb",
     "libsql_client",
-    "sshtunnel"
+    "sshtunnel",
+    "docker",
+    "docker.errors",
+    "pyarrow",
+    "textual_fastdatatable"
 ]
 ignore_missing_imports = true
 

{sqlit_tui-1.0.2 → sqlit_tui-1.1}/settings.template.json

@@ -9,6 +9,7 @@
     "use_default_adapters": true,
     "connections": [],
     "drivers": {
+      "missing_all": false,
       "missing": [],
       "install_result": "real",
       "pipx": "auto"