s3rds 0.3.0__tar.gz → 0.3.2__tar.gz

{s3rds-0.3.0 → s3rds-0.3.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: s3rds
-Version: 0.3.0
+Version: 0.3.2
 Summary: A truly serverless RDS on your own AWS account: Lambda URL endpoint, SQLite on S3, ≈ $0 when idle. Drivers named after the standard clients: s3rds.sqlite, s3rds.pymysql, s3rds.psycopg2; SQLAlchemy via sqlite+s3rds://, Django via ENGINE s3rds.sqlite.
 Author: Frank Zhang
 License: MIT
@@ -24,6 +24,8 @@ Requires-Python: >=3.9
 Description-Content-Type: text/markdown
 Requires-Dist: sqlglot<31,>=30.24
 Provides-Extra: mysql
+Provides-Extra: server
+Requires-Dist: sqlean.py==3.50.4.5; extra == "server"
 Provides-Extra: sqlalchemy
 Requires-Dist: SQLAlchemy<2.1,>=2.0; extra == "sqlalchemy"
 Provides-Extra: django
@@ -45,23 +47,23 @@ Requires-Dist: Django<6.2,>=6.1; extra == "django"
 
 Everything else stays: models, queries, cursors, transactions. For all of them: one writer at a time, every commit
 uploads the whole file (a few hundred ms), so keep a database under ~20 MB. Moving to RDS later is the same change
-backwards (`import pymysql`, `mysql+pymysql://`, `django.db.backends.mysql`). Refused features raise
+backwards (`import pymysql`, `import psycopg2`, `mysql+pymysql://`, `django.db.backends.mysql`). Refused features raise
 `NotSupportedError` — never silently different.
 
 ### The server: deploy once, ≈ $0 when idle
 
 You need an s3rds server in your own AWS account — a Lambda Function URL and an S3 bucket, nothing running
-while nobody uses it. Deploy it once with Terraform or CloudFormation from the
+while nobody uses it. Deploy it once with Terraform from the
 [main repository](https://github.com/cloudformer/s3rds#quick-start). Same as any driver needs its database.
 
 **Python drivers for [s3rds](https://github.com/cloudformer/s3rds) — a truly serverless RDS:
 a Lambda URL as your database endpoint, SQLite on S3, ≈ $0 when idle.**
 
-One install, one dependency (sqlglot, used only by `s3rds.pymysql`). Each driver is a submodule **named after the standard
+One install, one dependency (sqlglot, used only by `s3rds.pymysql` and `s3rds.psycopg2`). Each driver is a submodule **named after the standard
 client it mirrors**, so moving to a real database is a one-line import change and nothing else:
 
 ```bash
-pip install s3rds    # s3rds.sqlite, s3rds.pymysql, sqlite+s3rds:// for SQLAlchemy, ENGINE s3rds.sqlite for Django
+pip install s3rds    # s3rds.sqlite, s3rds.pymysql, s3rds.psycopg2, sqlite+s3rds:// for SQLAlchemy, ENGINE s3rds.sqlite for Django
 ```
 
 ```python
@@ -134,6 +136,7 @@ conversion in queries (keep `TIME_ZONE` equal to the connection's), `__regex`, `
   server (stale keep-alive connection). Timeouts raise an error with an explicit "result unknown".
 - `s3rds.pymysql` raises pymysql-style exceptions with MySQL error codes (1062, 1146, 1054, 1064, …);
   unsupported MySQL features raise `NotSupportedError` instead of misbehaving silently.
+- `s3rds.psycopg2` raises psycopg2's classes (`s3rds.psycopg2.errors.UniqueViolation`, …) with the SQLSTATE in `pgcode`.
 
 ## Versions
 
@@ -143,7 +146,7 @@ What the report was verified with; the full report: [REPORT.md](https://github.c
 |---|---|---|
 | Python (client) | 3.9 – 3.13: regression suite on 3.9.6, full comparison on 3.13.7 | `requires-python = ">=3.9"` |
 | Server runtime | AWS Lambda `python3.12` | `terraform/main.tf` |
-| SQLite (server engine) | 3.50.4, shipped in the Lambda zip (the runtime's own is 3.40.0) | `src/db/requirements.txt`: `sqlean.py==3.50.4.5` |
+| SQLite (server engine) | 3.50.4, shipped in the Lambda zip (the runtime's own is 3.40.0) | extra `pip install "s3rds[server]"` = `sqlean.py==3.50.4.5` |
 | sqlglot (MySQL translation) | 30.24 | dependency `sqlglot>=30.24,<31` |
 | SQLAlchemy | 2.0, tested on 2.0.55 | extra `pip install "s3rds[sqlalchemy]"` = `SQLAlchemy>=2.0,<2.1` |
 | Django | 6.1, tested on 6.1.2 (Python ≥ 3.12) | extra `pip install "s3rds[django]"` = `Django>=6.1,<6.2` |

{s3rds-0.3.0 → s3rds-0.3.2}/README.md

@@ -14,23 +14,23 @@
 
 Everything else stays: models, queries, cursors, transactions. For all of them: one writer at a time, every commit
 uploads the whole file (a few hundred ms), so keep a database under ~20 MB. Moving to RDS later is the same change
-backwards (`import pymysql`, `mysql+pymysql://`, `django.db.backends.mysql`). Refused features raise
+backwards (`import pymysql`, `import psycopg2`, `mysql+pymysql://`, `django.db.backends.mysql`). Refused features raise
 `NotSupportedError` — never silently different.
 
 ### The server: deploy once, ≈ $0 when idle
 
 You need an s3rds server in your own AWS account — a Lambda Function URL and an S3 bucket, nothing running
-while nobody uses it. Deploy it once with Terraform or CloudFormation from the
+while nobody uses it. Deploy it once with Terraform from the
 [main repository](https://github.com/cloudformer/s3rds#quick-start). Same as any driver needs its database.
 
 **Python drivers for [s3rds](https://github.com/cloudformer/s3rds) — a truly serverless RDS:
 a Lambda URL as your database endpoint, SQLite on S3, ≈ $0 when idle.**
 
-One install, one dependency (sqlglot, used only by `s3rds.pymysql`). Each driver is a submodule **named after the standard
+One install, one dependency (sqlglot, used only by `s3rds.pymysql` and `s3rds.psycopg2`). Each driver is a submodule **named after the standard
 client it mirrors**, so moving to a real database is a one-line import change and nothing else:
 
 ```bash
-pip install s3rds    # s3rds.sqlite, s3rds.pymysql, sqlite+s3rds:// for SQLAlchemy, ENGINE s3rds.sqlite for Django
+pip install s3rds    # s3rds.sqlite, s3rds.pymysql, s3rds.psycopg2, sqlite+s3rds:// for SQLAlchemy, ENGINE s3rds.sqlite for Django
 ```
 
 ```python
@@ -103,6 +103,7 @@ conversion in queries (keep `TIME_ZONE` equal to the connection's), `__regex`, `
   server (stale keep-alive connection). Timeouts raise an error with an explicit "result unknown".
 - `s3rds.pymysql` raises pymysql-style exceptions with MySQL error codes (1062, 1146, 1054, 1064, …);
   unsupported MySQL features raise `NotSupportedError` instead of misbehaving silently.
+- `s3rds.psycopg2` raises psycopg2's classes (`s3rds.psycopg2.errors.UniqueViolation`, …) with the SQLSTATE in `pgcode`.
 
 ## Versions
 
@@ -112,7 +113,7 @@ What the report was verified with; the full report: [REPORT.md](https://github.c
 |---|---|---|
 | Python (client) | 3.9 – 3.13: regression suite on 3.9.6, full comparison on 3.13.7 | `requires-python = ">=3.9"` |
 | Server runtime | AWS Lambda `python3.12` | `terraform/main.tf` |
-| SQLite (server engine) | 3.50.4, shipped in the Lambda zip (the runtime's own is 3.40.0) | `src/db/requirements.txt`: `sqlean.py==3.50.4.5` |
+| SQLite (server engine) | 3.50.4, shipped in the Lambda zip (the runtime's own is 3.40.0) | extra `pip install "s3rds[server]"` = `sqlean.py==3.50.4.5` |
 | sqlglot (MySQL translation) | 30.24 | dependency `sqlglot>=30.24,<31` |
 | SQLAlchemy | 2.0, tested on 2.0.55 | extra `pip install "s3rds[sqlalchemy]"` = `SQLAlchemy>=2.0,<2.1` |
 | Django | 6.1, tested on 6.1.2 (Python ≥ 3.12) | extra `pip install "s3rds[django]"` = `Django>=6.1,<6.2` |

{s3rds-0.3.0 → s3rds-0.3.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "s3rds"
-version = "0.3.0"
+version = "0.3.2"
 description = "A truly serverless RDS on your own AWS account: Lambda URL endpoint, SQLite on S3, ≈ $0 when idle. Drivers named after the standard clients: s3rds.sqlite, s3rds.pymysql, s3rds.psycopg2; SQLAlchemy via sqlite+s3rds://, Django via ENGINE s3rds.sqlite."
 readme = "README.md"
 requires-python = ">=3.9"
@@ -29,6 +29,7 @@ dependencies = ["sqlglot>=30.24,<31"]
 
 [project.optional-dependencies]
 mysql = []  # kept so that pip install "s3rds[mysql]" from 0.1.x keeps working
+server = ["sqlean.py==3.50.4.5"]      # the Lambda: s3rds.server + SQLite 3.50.4 instead of the runtime's 3.40.0
 sqlalchemy = ["SQLAlchemy>=2.0,<2.1"]   # the series the compatibility report verified; pip install "s3rds[sqlalchemy]"
 django = ["Django>=6.1,<6.2"]          # the same for Django (ENGINE "s3rds.sqlite"); Django 6.1 needs Python >= 3.12
 
@@ -44,14 +45,17 @@ Changelog = "https://github.com/cloudformer/s3rds/blob/main/CHANGELOG.md"
 Issues = "https://github.com/cloudformer/s3rds/issues"
 
 [tool.setuptools]
-packages = ["s3rds", "s3rds.sqlite", "s3rds.psycopg2"]
+packages = ["s3rds", "s3rds.sqlite", "s3rds.psycopg2", "s3rds.server"]
+
+[tool.setuptools.package-data]
+"s3rds.server" = ["index.html"]
 
 # The versions tests/compat/REPORT.md was verified with; README.md, README.zh.md and client/README.md state the same.
 [tool.s3rds.verified]
 python = ["3.9.6", "3.13.7"]       # the client: regression suite on 3.9.6, the full comparison on 3.13.7
 lambda_runtime = "python3.12"      # the server (terraform/main.tf)
 sqlite = "3.50.4"                  # the server's engine, shipped in the Lambda zip (the runtime's own is 3.40.0)
-sqlean = "3.50.4.5"                # sqlean.py, which carries it (src/db/requirements.txt)
+sqlean = "3.50.4.5"                # sqlean.py, which carries it (extra "server")
 sqlglot = "30.24.0"
 sqlalchemy = "2.0.55"
 django = "6.1.2"

s3rds-0.3.2/s3rds/server/__init__.py

@@ -0,0 +1,5 @@
+"""s3rds server: the Lambda behind the endpoint. pip install "s3rds[server]" (adds the pinned SQLite engine).
+
+Lambda handler: s3rds.server.lambda_function.lambda_handler. Not imported here: lambda_function reads its
+environment (DB_BUCKET, ...) at import time, and a client never needs it.
+"""