--- DarthVader/CHANGELOG	2014/09/16 20:01:25	1.2
+++ DarthVader/CHANGELOG	2014/10/10 13:34:59	1.3
@@ -1,3 +1,17 @@
 v10r17 	:	used for processing at NA and MEPHI 
 v10r18	:	BUG FIXED: crash (ToF, probably also CALO and ORB) when reprocessing full file (probably any reprocessing) without extended tracks
 		New methods for tracks retrieving added in CaloLevel2.h, ToFLevel2.h and OrbitalInfo.h
+v10r19	:	testing purpose (ExtTrack processing only)
+v10r20	:	BUG FIXED: crash due to new default in MySQL >=5.5.5, 
+		The query that is failing is something like: 
+		select ID_ROOT_L0, FROM_TIME, TO_TIME, EV_ROOT from GL_CALO_CALIB where SECTION=0 and VALIDATION=1 ORDER BY ABS(1322051607-FROM_TIME) asc limit 1
+		this issue and it seems that is related to the "NO_UNSIGNED_SUBTRACTION" mode of MySQL.
+		"As of MySQL 5.5.5, overflow during numeric expression evaluation results in
+		an error. For example, the largest signed BIGINT value is
+		9223372036854775807, so the following expression produces an error."
+		You can find other infos about this here
+		http://dev.mysql.com/doc/refman/5.5/en/server-sql-mode.html
+		essentialy now, by default, subtraction between integer operands produces an
+		UNSIGNED result if any operand isUNSIGNED. This is something that I think is
+		weird and in the code there is not such an assumption of course, I expect
+		that the subtraction between two unsigned integer COULD result in a negative number...