I don't use transactions in pyramid , but am intrigued... 1. Assuming you're using sqlalchemy, and the interface to transaction is provided by the zope.sqlalchemy package , is there any actual database transaction ( begin; rollback ) for non-database requests ? ( ie, is the "transaction" entirely in pyramid, and never in postgreqsql ? )
2. If the above is the case, and you have multiple database connections ( for example, a READ/WRITE or SLAVE/MASTER ) would you be able to escape most issues of long running requests, because the database transaction blocking would only be on the write/master and not the read/slave ? -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/groups/opt_out.
