Mercurial > p > roundup > code
view website/issues/html/_generic.collision.html @ 5086:2b551b6b0830
issue2550549 Postgres error on message templating
Exception gets thrown and not captured if nodeid is too large on
postgres. Added a check in rdbms_common layer that max nodeid is <
2^31 -1. This is also the limit for INTEGER on MySql. SqlLite can
support up to 2^63-1, but I chose the smallest common denominator.
Large nodeid should now returns no such id rather than a stack trace.
Patch idea from: martin.v.loewis. (John Rouillard)
This fixes the reason for patches:
https://hg.python.org/tracker/roundup/rev/1548763e8273
and
https://hg.python.org/tracker/roundup/rev/eb3be57f1ef2
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Sat, 18 Jun 2016 22:48:21 -0400 |
| parents | c2d0d3e9099d |
| children | 4ac0bbb3e440 |
line wrap: on
line source
<tal:block metal:use-macro="templates/page/macros/icing"> <title metal:fill-slot="head_title" i18n:translate="" ><span tal:replace="python:context._classname.capitalize()" i18n:name="class" /> Edit Collision - <span i18n:name="tracker" tal:replace="config/TRACKER_NAME" /></title> <tal:block metal:fill-slot="body_title" i18n:translate="" ><span tal:replace="python:context._classname.capitalize()" i18n:name="class" /> Edit Collision</tal:block> <td class="content" metal:fill-slot="content" i18n:translate=" There has been a collision. Another user updated this node while you were editing. Please <a href='${context}'>reload</a> the node and review your edits. "><span tal:replace="context/designator" i18n:name="context" /> </td> </tal:block>