simple-module-cli 0.0.17__tar.gz → 0.0.18__tar.gz

{simple_module_cli-0.0.17 → simple_module_cli-0.0.18}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: simple_module_cli
-Version: 0.0.17
+Version: 0.0.18
 Summary: Standalone scaffolder for the SimpleModule framework — `smpy new`, `smpy create-module`, plugin host.
 Project-URL: Homepage, https://github.com/antosubash/simple_module_python
 Project-URL: Repository, https://github.com/antosubash/simple_module_python

{simple_module_cli-0.0.17 → simple_module_cli-0.0.18}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "simple_module_cli"
-version = "0.0.17"
+version = "0.0.18"
 description = "Standalone scaffolder for the SimpleModule framework — `smpy new`, `smpy create-module`, plugin host."
 readme = "README.md"
 license = "MIT"

{simple_module_cli-0.0.17 → simple_module_cli-0.0.18}/simple_module_cli/skills/simple-module-creating/SKILL.md

@@ -68,7 +68,7 @@ class OrdersModule(ModuleBase):
     )
 ```
 
-`ModuleMeta.name` is load-bearing in three places: the Postgres schema name, the SQLite `__tablename__` prefix you author, and the PascalCase Inertia component namespace. So directory `blog_posts` → `name="BlogPosts"` → `inertia.render("BlogPosts/Index", ...)` → `pages/Index.tsx`. Mismatches fire diagnostic codes `SM003` (orphan page) / `SM004` (phantom render).
+`ModuleMeta.name` is load-bearing in two places: the `__tablename__` prefix you author and the PascalCase Inertia component namespace. So directory `blog_posts` → `name="BlogPosts"` → `inertia.render("BlogPosts/Index", ...)` → `pages/Index.tsx`. Mismatches fire diagnostic codes `SM003` (orphan page) / `SM004` (phantom render).
 
 For modules you intend to publish, also add `version=` (your module's semver) and `requires_framework=` (a PEP 440 spec for the framework API range, e.g. `">=1.0,<2.0"`) so the host can reject incompatible installs at boot.
 

{simple_module_cli-0.0.17 → simple_module_cli-0.0.18}/simple_module_cli/skills/simple-module-database/SKILL.md

@@ -18,26 +18,14 @@ from simple_module_db.mixins import AuditMixin
 Base = create_module_base("orders")
 
 class Order(Base, AuditMixin, table=True):
-    __tablename__ = "orders_order"   # SQLite-safe prefix; required (see below)
+    __tablename__ = "orders_order"   # module-name prefix; required
     id: int | None = Field(default=None, primary_key=True)
     name: str = Field(max_length=200)
 ```
 
-The provider is auto-detected from `SM_DATABASE_URL`. Pin it explicitly only in tests:
+## Table naming
 
-```python
-from simple_module_db.base import create_module_base, DatabaseProvider
-Base = create_module_base("orders", provider=DatabaseProvider.SQLITE)
-```
-
-## Postgres vs SQLite — the same code, different physical layout
-
-| Provider | Physical placement | Required convention |
-|---|---|---|
-| **PostgreSQL** | One **schema** per module (`orders.order`, `users.user`). Created automatically. | Set `__tablename__` to a name unique within the module. |
-| **SQLite** | Single schema. Cross-module name collisions break things. | Prefix `__tablename__` with the module name (`orders_order`). |
-
-Always include the module-name prefix in `__tablename__`. It's redundant on Postgres (the schema already namespaces it) and **required** on SQLite. Code that runs in CI on SQLite and prod on Postgres needs both — pick the prefix.
+All modules — on Postgres and SQLite alike — share the host's single schema. Cross-module name collisions break things, so `__tablename__` must be prefixed with the module name (e.g. `orders_order`, `users_user`). The framework does not enforce the prefix; it's a convention the migrations and diagnostics rely on.
 
 ## Mixins