pyeventsourcing / eventsourcing-sqlalchemy Goto Github PK

Is there a plan to make this not require SQLAlchemy 1.4? Is there breakage in v2.0 that prevents the library from working?

During an exploratory test

    os.environ['INFRASTRUCTURE_FACTORY'] = 'eventsourcing_sqlalchemy.factory:Factory'
    os.environ["SQLALCHEMY_URL"] = "sqlite:///wtf.sqlite3"

and running a demo application as described in the readme, we see a wtf.sqlite3 DB file created correctly while

    os.environ["PERSISTENCE_MODULE"] = "eventsourcing_sqlalchemy"
    os.environ["SQLALCHEMY_URL"] = "sqlite:///wtf.sqlite3"

does not cause the same effect.
Any ideas what could be the root cause?
Also we noticed that

    os.environ["PERSISTENCE_MODULE"] = "any_random_string"

does not make the application crash, while changes to INFRASTRUCTURE_FACTORY are validated right away.

Hi @johnbywater

First, thanks for promoting and supporting eventsourcing through your excellent work!

In my scenario, I have an existing Postgres session (see code snippet below). I would like to re-use this session in my application recorder, which is derived from SQLAlchemyApplicationRecorder. The reason for this is that I do CRUD operations in the database first (outside of the scope of the eventsourced application), and then change my eventsourced application; and I need to achieve atomicity for both my CRUD changes and the eventsourced changes together.

I looked at the infrastructure factory in eventsourcing_sqlalchemy/factory.py, and the SQLAlchemyDatastore, but could not find out how to inject my own session.

Can you help?

This is how I define SessionLocal, which I then use to create my session, outside of my eventsourced application:

from sqlalchemy import create_engine
from sqlalchemy.orm import sessionmaker

engine = create_engine(url) : Engine
SessionLocal = sessionmaker(autocommit=False, autoflush=False, bind=engine)

I'd appreciate any hints on this!