muscles-data-sqlalchemy

SQLAlchemy adapter package for muscles-data.

This package is intentionally separate from muscles-data: the core package owns typed ports, resource runtime and diagnostics, while this package owns the SQLAlchemy-backed SqlResourcePort adapter.

Use this package when a project wants direct SQLAlchemy sessions through the same data resource runtime without wiring muscles-data-sql first.

Related packages

• Core runtime and port contracts: muscles-data
• Elasticsearch search adapter: muscles-data-elasticsearch
• OpenSearch search adapter: muscles-data-opensearch
• Redis key-value/lock/stream adapter: muscles-data-redis
• Qdrant vector adapter: muscles-data-qdrant
• MongoDB document-store adapter: muscles-data-mongodb
• S3 object-store adapter: muscles-data-s3
• Executable example: example_data_sqlalchemy_1

Usage

Register this adapter once in the application composition root when building the shared DataAdapterCatalog, alongside other configured adapters:

catalog.register(SqlAlchemySqlResourceFactory())

The sql.local resource itself is declared in the application's central data.resources configuration shown below. A package resolves the port from the existing runtime; it does not build another catalog or DataRuntime:

from muscles.data.ports import SqlResourcePort

sql = app.resource.connect("sql.local", SqlResourcePort)

Resource config stays in the project:

data:
  resources:
    sql.local:
      type: sqlalchemy
      url: sqlite:///:memory:
      name: local_sqlite
      pool_pre_ping: true
      native_client: false

data.resources.list does not create the engine. The engine/session factory is created lazily by session(), session_factory(), explicit native access or data.doctor.

Application code should use SqlResourcePort; direct engine/session-factory access is only an advanced escape hatch with native_client: true.

See muscular-example/example_data_sqlalchemy_1 for an executable example.