Hi Kristoffer,
thanks for this patches, info. Means this, that OTRS (application) works just with this one Kernel/System/Ticket/Article.pm change on Oracle?
Thanks,
-Martin
Kristoffer Gleditsch wrote:
I've now upgraded our customer's OTRS/Oracle installation to 1.3.2. This reduced the number of patches needed quite a bit, although we're not done testing it yet. I've attached the patches I needed (apart from the obviously site-specific ones, like stylesheets and 'use lib'). The updated schema file is also attached.
Note that I've made CLOBs of the fields having the datatype TEXT in PostgreSQL. Since the "=" operator doesn't like CLOBs, the patch below changes "=" to "LIKE" in some string comparison statements. I think that should work just as well as "=" on all databases.
The patches I've currently applied to my installation:
------------------------------------------------------------------------
Index: Article.pm =================================================================== --- Article.pm (.../tags/otrs-1.3.2/otrs/Kernel/System/Ticket/Article.pm) (revision 37) +++ Article.pm (.../branches/installed-1.3.2/otrs/Kernel/System/Ticket/Article.pm) (revision 37) @@ -355,10 +355,10 @@ $SQL .= "a_message_id = '$Param{MessageID}' AND "; } if ($Param{From}) { - $SQL .= "a_from = '$Param{From}' AND "; + $SQL .= "a_from LIKE '$Param{From}' AND "; } if ($Param{Subject}) { - $SQL .= "a_subject = '$Param{Subject}' AND "; + $SQL .= "a_subject LIKE '$Param{Subject}' AND "; } $SQL .= " incoming_time = '$Param{IncomingTime}'"; # start query
------------------------------------------------------------------------
Index: initial_insert.sql
===================================================================
--- initial_insert.sql (.../tags/otrs-1.3.2/otrs/scripts/database/initial_insert.sql) (revision 37)
+++ initial_insert.sql (.../branches/installed-1.3.2/otrs/scripts/database/initial_insert.sql) (revision 37)
@@ -206,6 +206,14 @@
-- did not receive this file, see http://www.gnu.org/licenses/gpl.txt.
-- --
+-- --
+-- If you use Oracle and shove this file through sql*plus, you might
+-- want to set this, to disable the substition mechanism which is
+-- otherwise triggered by some of the notification strings:
+-- --
+set define off;
+-- --
+
-- table valid
INSERT INTO valid
(name, create_by, create_time, change_by, change_time)
@@ -634,7 +642,7 @@
INSERT INTO standard_response
(name, text, valid_id, create_by, create_time, change_by, change_time)
VALUES
- ('empty answer', '', 1, 1, current_timestamp, 1, current_timestamp);
+ ('empty answer', ' ', 1, 1, current_timestamp, 1, current_timestamp);
INSERT INTO standard_response
(name, text, valid_id, create_by, create_time, change_by, change_time)
VALUES
------------------------------------------------------------------------
The only other gotcha I can think of is that the session database shouldn't be called "session". The schema calls it "sessions", but this must be reflected in Kernel/Config.pm.
Also, is this the right place to ask about the "commercial support" list on http://otrs.org/support/? The company I work for (Linpro AS, www.linpro.no) has customized and supported OTRS for several customers, and would appreciate being mentioned in this list. :)
Regards,
_______________________________________________ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
