From 4e2b549a28f09fdc749f380a3e8c458c4ff53273 Mon Sep 17 00:00:00 2001
From: =?utf8?q?Sven=20Sch=C3=B6ling?= <s.schoeling@linet-services.de>
Date: Fri, 2 Jul 2010 14:20:19 +0200
Subject: [PATCH] RP->aging: storno kann auch NULL sein
MIME-Version: 1.0
Content-Type: text/plain; charset=utf8
Content-Transfer-Encoding: 8bit

Fehler trat auf, weil Kreditorenbuchungen nicht sicher gehen, dass storno auf false steht.
Dieser Fix behebt das für diesen speziellen Fall.

storno sollte später auf NOT NULL gesetzt werden.
---
 SL/RP.pm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/SL/RP.pm b/SL/RP.pm
index 81637ca5b..88f4ebe55 100644
--- a/SL/RP.pm
+++ b/SL/RP.pm
@@ -1198,7 +1198,7 @@ sub aging {
          AND (exchangerate.transdate = ${arap}.transdate)) AS exchangerate
     FROM ${arap}, ${ct}
     WHERE ((paid != amount) OR (datepaid > (date $todate) AND datepaid is not null))
-      AND (${arap}.storno IS FALSE)
+      AND NOT COALESCE (${arap}.storno, 'f')
       AND (${arap}.${ct}_id = ${ct}.id)
       AND (${ct}.id = ?)
       AND (transdate <= (date $todate) $fromwhere )
-- 
2.20.1