I will try to remove crud_sessionmaker and call CRUD(DBSession, Table).create directly. This will use the usual request.dbsession
check it out pyramid_sacrud==0.1.2 version
I already have a request.dbsession set, that's why I was wondering if I could use the crud_sessionmaker in my whole app without expecting problems
It would be better if pyramid_sacrud doesn't affect the request object at all
I removed crud_sessionmaker from new version (0.1.2). Now, this does not affect on request.dbsession. You can simply overwrite request.dbsession. Overall, I think even to get rid of request method from pyramid_sacrud, it will be more clean. And will add features to tables with different DBSession (for example different database).