Seems like default behavior is sane to me fwiw.
Laurence Rowe laurencer...@gmail.com wrote:
By default the zope.sqlalchemy extension only commits if it thinks changes
have been made (by listening for orm events.) If you go outside of that you
need to use mark_changed on the session, or switch
Thank you for the suggestion, Vincent :-)
But I have exactly the same development.ini file on both sides, and it
includes pyramid_tm...
I have the same versions of the important modules on both sides (Pyramid
1.4.3, pyramid-tm 0.7, transaction 1.4.1, zope.sqlalchemy 0.7.3,
sqlalchemy 0.8.2,
By default the zope.sqlalchemy extension only commits if it thinks changes
have been made (by listening for orm events.) If you go outside of that you
need to use mark_changed on the session, or switch the behaviour off
completely by using 'changed' as the initial state. See the example in
Hello list,
I'm trying to understand what's going on here:
- 2 Pyramid development servers, running almost identical versions of OS
and software (only minor versions may differ, e.g. FreeBSD 9.1 vs 9.2,
PostgreSQL 9.2 vs 9.3, etc.)
- Same Pyramid app deployed on both servers
- On server #1,
In your developement.ini (or whichever .ini file you are using) are you
making sure to include the pyramid_tm package as part of the
pyramid.includes directive?
[app:main]
...
pyramid.includes =
pyramid_tm
...
-Vincent
On Sat, Oct 5, 2013 at 8:40 AM, Laurent DAVERIO ldave...@gmail.com
