alt-python-pydbc-sqlite
pydbc driver for SQLite via the Python standard-library sqlite3 module. Zero external dependencies.
Installation
uv add alt-python-pydbc-sqlite
URL formats
| Format | Description |
|---|---|
pydbc:sqlite::memory: |
In-memory database (isolated per connection) |
pydbc:sqlite:./path/to/db |
File-backed database |
pydbc:sqlite:/absolute/path/to/db |
File-backed database (absolute path) |
Usage
import pydbc_sqlite # registers SQLiteDriver with DriverManager
from pydbc_core import DriverManager
conn = DriverManager.get_connection("pydbc:sqlite::memory:")
stmt = conn.create_statement()
rs = stmt.execute_query("SELECT 1 AS n")
print(rs.rows) # [(1,)]
conn.close()
Parameterised queries
# Positional parameters
stmt = conn.create_statement()
rs = stmt.execute_query("SELECT * FROM users WHERE id = ?", (42,))
# Named parameters
rs = stmt.execute_query("SELECT * FROM users WHERE id = :id", {"id": 42})
Prepared statements
ps = conn.prepare_statement("INSERT INTO users (name, email) VALUES (?, ?)")
ps.execute_update(("Alice", "alice@example.com"))
ps.execute_update(("Bob", "bob@example.com"))
conn.commit()
Paramstyle note
sqlite3 uses qmark (?) placeholders internally. pydbc accepts both ?
(positional) and :name (named) syntax and translates automatically — you never
need to know which style the underlying driver uses.
Documentation
License
MIT
1 maintainer
Metadata
1 maintainer
Release files for alt-python-pydbc-sqlite 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| alt_python_pydbc_sqlite-1.1.0.tar.gz | 3.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| alt_python_pydbc_sqlite-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.3 kB
Release files / alt_python_pydbc_sqlite-1.1.0.tar.gz
| Download URL | alt_python_pydbc_sqlite-1.1.0.tar.gz |
|---|---|
| Size | 3.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1a6126e3be8353fdaade72a6125fa8ec530621ac186156453f279e0561df375f
|
|
BLAKE2b-256 checksum How to use checksums |
f609f70da971f775ab8a3d05b11c52a709cabeffc1e48005c21dfe463262daa5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.2 {"installer":{"name":"uv","version":"0.11.2","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / alt_python_pydbc_sqlite-1.1.0-py3-none-any.whl
| Download URL | alt_python_pydbc_sqlite-1.1.0-py3-none-any.whl |
|---|---|
| Size | 3.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
738e0005a9745632bf077c504b13278393815e951150663a173bf4e1743e7839
|
|
BLAKE2b-256 checksum How to use checksums |
6aa2d09b135c529482890cfb551609257aab93ae8c3c966de2d6ce3952d8a1ed
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.2 {"installer":{"name":"uv","version":"0.11.2","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for alt-python-pydbc-sqlite 1.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
