Mercurial > p > roundup > code
comparison doc/upgrading.txt @ 4211:61cf00ca920a
Process each message through the mail gateway as a separate transaction.
The mail-gateway used to process messages fetched, e.g., via imap in a
single big transaction. Now we process each message coming in via the
mail-gateway in its own transaction. Regression-tests passed.
See also discussion:
http://thread.gmane.org/gmane.comp.bug-tracking.roundup.user/9500
| author | Ralf Schlatterbeck <schlatterbeck@users.sourceforge.net> |
|---|---|
| date | Tue, 14 Jul 2009 09:10:43 +0000 |
| parents | ad57b06af972 |
| children | a57ced3a4bb6 |
comparison
equal
deleted
inserted
replaced
| 4202:e47ec982645b | 4211:61cf00ca920a |
|---|---|
| 13 | 13 |
| 14 .. contents:: | 14 .. contents:: |
| 15 | 15 |
| 16 Migrating from 1.4.x to 1.4.9 | 16 Migrating from 1.4.x to 1.4.9 |
| 17 ============================= | 17 ============================= |
| 18 | |
| 19 Customized MailGW Class | |
| 20 ----------------------- | |
| 21 | |
| 22 If you have customized the MailGW class in your tracker: The new MailGW | |
| 23 class opens the database for each message in the method handle_message | |
| 24 (instance.open) instead of passing the opened database as a parameter to | |
| 25 the MailGW constructor. The old handle_message has been renamed to | |
| 26 _handle_message. The new method opens the database and wraps the call to | |
| 27 the old method into a try/finally. | |
| 28 | |
| 29 Your customized MailGW class needs to mirror this behavior. | |
| 18 | 30 |
| 19 Fix the "remove" button in issue files and messages lists | 31 Fix the "remove" button in issue files and messages lists |
| 20 --------------------------------------------------------- | 32 --------------------------------------------------------- |
| 21 | 33 |
| 22 The "remove" button(s) in the issue messages list needs to be altered. Find | 34 The "remove" button(s) in the issue messages list needs to be altered. Find |