From e2bfda48dec336d7c4b90a918c6d6d25c974f04c Mon Sep 17 00:00:00 2001
From: =?utf8?q?Bernd=20Ble=C3=9Fmann?= <bernd@kivitendo-premium.de>
Date: Wed, 27 Jan 2021 12:14:33 +0100
Subject: [PATCH] Revert "POD fix: Rose Syntax"

ilike gibt es doch.

This reverts commit 95f21f71c1c5c2f6cf6a281a0174d8f247be1135.
---
 SL/Controller/Helper/ParseFilter.pm | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/SL/Controller/Helper/ParseFilter.pm b/SL/Controller/Helper/ParseFilter.pm
index e1b621f16..8b68ee56e 100644
--- a/SL/Controller/Helper/ParseFilter.pm
+++ b/SL/Controller/Helper/ParseFilter.pm
@@ -297,11 +297,10 @@ customer. L<Rose::DB::Object> allows you to search for these by filtering them p
 
   query => [
     'customer.name'          => 'John Doe',
-    'department.description' => [ like => '%Sales%' ],
-    'orddate'                => { lt    => DateTime->today },
+    'department.description' => [ ilike => '%Sales%' ],
+    'orddate'                => [ lt    => DateTime->today ],
   ]
 
-
 Unfortunately, if you specify them in your form as these strings, the form
 parser will convert them into nested structures like this:
 
-- 
2.20.1