Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Matheo13
    @Matheo13
    Hi, I'm not sure to be in the right place but I didn't saw any other gitter room on pyramid
    I just have question regarding AuthTktAuthenticationPolicy function
    uralbash
    @uralbash
    Hi, feel free to the question, I will try to answer, in my competence. But think this question better to ask in the IRC chat room #pyramid
    tonthon
    @tonthon
    Hi, I'm wondering what the crud_sessionmaker adds to the orm session?
    I'm trying to integrate pyramid_sacrud in an existing project setting a request.dbsession
    so I get an error
    tonthon
    @tonthon
    I'm wondering if I replace my session maker by sacrud's one, may I expect some troubleshootings ?
    mine is built this way : DBSESSION = scoped_session(sessionmaker(extension=ZopeTransactionExtension()))
    uralbash
    @uralbash
    Your own DBSESSION an DBSession in pyramid_sacrud (https://github.com/ITCase/pyramid_sacrud/blob/master/pyramid_sacrud/includes/database.py#L21) do not affect each other
    but if you replace an existing object request.dbsession it may raise error, because crud_sessionmaker adds to dbsession method sacrud (http://sacrud.readthedocs.org/en/master/plain_usage.html#wraps-your-zope-sqlalchemy-session). It's work like this dbsession.sacrud(Table).create ...
    uralbash
    @uralbash
    I will try to remove crud_sessionmaker and call CRUD(DBSession, Table).create directly. This will use the usual request.dbsession
    uralbash
    @uralbash
    check it out pyramid_sacrud==0.1.2 version
    tonthon
    @tonthon
    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
    uralbash
    @uralbash
    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).
    tonthon
    @tonthon
    I'll give it a try this week
    uralbash
    @uralbash
    t
    t