mainsequence 4.2.14__tar.gz → 4.2.25__tar.gz

{mainsequence-4.2.14/mainsequence.egg-info → mainsequence-4.2.25}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mainsequence
-Version: 4.2.14
+Version: 4.2.25
 Summary: Main Sequence SDK 
 Author-email: Main Sequence GmbH <dev@main-sequence.io>
 License: MainSequence GmbH SDK License Agreement
@@ -68,7 +68,7 @@ Requires-Dist: pydantic
 Requires-Dist: pytz
 Requires-Dist: pyyaml
 Requires-Dist: requests
-Requires-Dist: sqlalchemy
+Requires-Dist: sqlalchemy<3,>=2
 Requires-Dist: structlog
 Requires-Dist: tqdm
 Requires-Dist: typer

{mainsequence-4.2.14 → mainsequence-4.2.25}/agent_scaffold/skills/data_publishing/data_nodes/SKILL.md

@@ -148,7 +148,7 @@ class Base(DeclarativeBase):
 
 class PricesTable(PlatformTimeIndexMetaData, Base):
     __metatable_namespace__ = "<domain_namespace>"
-    __metatable_identifier__ = "<table_identifier>"
+    __metatable_identifier__ = "<project_name>.<table_identifier>"
     __metatable_extra_hash_components__ = {"storage_name": "<stable_storage_name>"}
     __metatable_description__ = (
         "Daily close prices keyed by asset unique identifier for portfolio and "
@@ -387,9 +387,9 @@ DataNode storage table needs a platform-managed FK, use
 `ForeignKey(Target.__table__.c.uid)`, table fullnames, or explicit target UID
 maps in DataNode examples.
 
-Do not ask users to name these foreign keys. `MetaTableForeignKey(...)` derives
-a stable contract name when `name` is omitted; `name=...` is only for deliberate
-overrides.
+Do not ask users to name these foreign keys. Platform-managed
+`MetaTableForeignKey(...)` contracts store logical relationships only. Alembic,
+SQLAlchemy, and the database own physical FK constraint names.
 
 Registration of the storage class follows the MetaTable migration lifecycle.
 Migration tooling recursively resolves/registers unresolved FK target model
@@ -402,6 +402,9 @@ Do not add DataNode configuration fields just to mutate storage metadata.
 
 Production-quality table identifiers, descriptions, labels, column docs, and
 foreign-key metadata belong to the storage class/MetaTable registration path.
+Prefix explicit table identifiers, explicit physical table names, and Alembic
+version table names with the project or package name rather than using bare
+names that can collide across projects.
 
 Do not put schema or published table metadata on the DataNode configuration.
 

{mainsequence-4.2.14 → mainsequence-4.2.25}/agent_scaffold/skills/data_publishing/meta_tables/SKILL.md

@@ -152,12 +152,17 @@ table. Do not use it for labels, descriptions, runtime options, test isolation,
 backend UIDs, data-source UIDs, or updater scope. Use `hash_namespace` for test
 or experiment isolation.
 
+Prefix explicit table identifiers, explicit physical table names, and Alembic
+version table names with the project or package name. Bare names such as
+`Account`, `Asset`, or `alembic_version` can collide across projects sharing an
+organization or database schema.
+
 Register through the class API:
 
 ```python
 class Account(PlatformManagedMetaTable, Base):
     __metatable_namespace__ = "sdk-examples"
-    __metatable_identifier__ = "Account"
+    __metatable_identifier__ = "sdk_examples.Account"
     __metatable_extra_hash_components__ = {"storage_name": "account"}
     __metatable_description__ = (
         "Customer account master records used to scope balances, holdings, and "
@@ -222,10 +227,9 @@ tooling resolves/registers unresolved target model classes, stores each
 returned `MetaTable` in a local process registry keyed by `storage_hash`, and
 uses the target `MetaTable.uid` in the child FK contract.
 
-Do not require users to provide foreign-key names. `MetaTableForeignKey(...)`
-accepts `name=...` only as an override; when omitted, the SDK derives a stable
-PostgreSQL-safe contract name from the child table and source column after the
-column is attached to the SQLAlchemy table.
+Do not require users to provide foreign-key names. Platform-managed
+`MetaTableForeignKey(...)` contracts store logical relationships only. Alembic,
+SQLAlchemy, and the database own physical FK constraint names.
 
 Use this pattern:
 
@@ -300,6 +304,9 @@ global identity. If it does not, the SDK derives the identifier from
 `[project].name` in `pyproject.toml` plus
 `<model.__module__>.<model.__qualname__>`. Pin an explicit identifier when a
 class is renamed or moved but must keep the same platform identity.
+When declaring an explicit identifier, explicit physical table name, or Alembic
+version table name, prefix it with the project or package name rather than using
+a bare table name.
 
 Do not ask users to construct backend migration payloads, call low-level
 migration request models, or use SDK helper functions directly. The backend