diff CHANGES.txt @ 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 d3d9d1402763
children 39af8a0f3446
line wrap: on
line diff
--- a/CHANGES.txt	Sat Jun 18 00:39:01 2016 -0400
+++ b/CHANGES.txt	Sat Jun 18 22:48:21 2016 -0400
@@ -113,6 +113,12 @@
   the codecs.
 - issue2550823 improve mailgw logging for node creation errors.
   Patch by r.david.murray (applied by John Rouillard).
+- 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. Large nodeid now return no such id error upstream.
+  Patch idea from: martin.v.loewis. (John Rouillard)
+
 
 2016-01-11: 1.5.1
 

Roundup Issue Tracker: http://roundup-tracker.org/