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 the behaviour off >completely by using 'changed' as the initial state. See the example in >https://pypi.python.org/pypi/zope.sqlalchemy > >(This seems to be more of a problem than it is worth, so a future version of >zope.sqlalchemy may change the default behaviour.) > >Laurence > >On Sunday, 6 October 2013 05:50:02 UTC-7, Eldav wrote: > >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, psycopg2 2.5.1, etc.) > >The mystery remain... (for now) > >Laurent. > > >Le 06/10/13 01:56, Vincent Catalano a �crit : >> 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 <ldav...@gmail.com >> <mailto:ldav...@gmail.com>> wrote: >> >> 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, database COMMITs are emitted automatically inside views, >> which is normal, but not on server #2. >> >> - On server #2, if I add a "transaction.commit()" at the end of a view, >> transactions are emitted (I thought it was supposed to raise an >> exception??) >> >> I'm rather baffled, to say the least. Would you have any hint as to what >> may be happening? >> >> Many thanks in advance, >> >> Laurent. >> >> -- >> 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 pylons-discus...@googlegroups.com >> <mailto:pylons-discuss%2bunsubscr...@googlegroups.com>. >> To post to this group, send email to pylons-...@googlegroups.com >> <mailto:pylons-...@googlegroups.com>. >> Visit this group at http://groups.google.com/group/pylons-discuss. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> >> >> -- >> Vincent Catalano >> Software Engineer and Web Ninja, >> (520).603.8944 >> >> -- >> 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 pylons-discus...@googlegroups.com. >> To post to this group, send email to pylons-...@googlegroups.com. >> Visit this group at http://groups.google.com/group/pylons-discuss. >> For more options, visit https://groups.google.com/groups/opt_out. > >-- >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 pylons-discuss+unsubscr...@googlegroups.com. >To post to this group, send email to pylons-discuss@googlegroups.com. >Visit this group at http://groups.google.com/group/pylons-discuss. >For more options, visit https://groups.google.com/groups/opt_out. -- 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 pylons-discuss+unsubscr...@googlegroups.com. To post to this group, send email to pylons-discuss@googlegroups.com. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/groups/opt_out.
