Bug fix: action.statuscode was in upper case.

diff --git a/src/database/create.sql b/src/database/create.sql
index 992f656..faeaecd 100644 (file)
--- a/src/database/create.sql
+++ b/src/database/create.sql
@@ -12,7 +12,10 @@
 -- DBA create the database and give access permissions.
 --
 --  $Log: create.sql,v $
---  Revision 1.6  2003-01-20 07:29:48  arjen
+--  Revision 1.7  2003-02-05 09:29:08  arjen
+--  Bug fix: action.statuscode was in upper case.
+--
+--  Revision 1.6  2003/01/20 07:29:48  arjen
 --  Added new tables to the database: parameter_class and parameter_notification
 --
 --  Revision 1.5  2003/01/18 08:46:48  arjen
@@ -33,25 +36,25 @@ CREATE TABLE "action"
 
 
 COPY "action" FROM stdin;
-1      Entry in the system     NEW     This indicates that a notification has been entered into the system.
-2      Display to user OPN     The notification has been displayed to the user. It doesn't mean that the user actually read the notification, but he/she should be aware. For that reason we consider the notification to be OPEN
-3      Remarks added   PEN     Remarks have been added to the notification.
-4      Priority changed manually       PEN     The priority of the notification has been changed by the user.
-5      Priority changed automatically  PEN     The priority of the notification has been changed by the system. This can be the result of an action by the user or an automatical escalation.
-6      Action taken    PEN     An action has been taken.
-7      Assignment to user      PEN     The notification has been assigned to an user.
-8      More information or research needed.    INV     The notification is relevant and will be handled, however more information or research will be needed. For that reason the status has been altered to UNDER INVESTIGATION.
-9      Investigation completed PEN     Investigation has been done. Information is available to fix the problem.
-10     Job output no longer valid      CLS     By making a newer job output a valid reference, this data has been obsoleted. Since it was a reference once the output isn't interesting anymore and thus the notification can be closed.
-11     Action taken - please verify    CLS     An action has been taken and things should have been resolved. Before the notification can be closed a verification has to be done. The new status is now VERIFY.
-12     Action not verified     PEN     A check has been done and the results were not good. New verification is needed. The status has been changed back to PEN.
-13     Action verified CLS     A check has been done and the results were approved. The notification has been closed.
-15     SMS sent        OPN     An SMS has been sent.
-14     E-mail sent     OPN     An e-mail has been sent.
-16     Fax sent        OPN     An fax has been sent.
+1      Entry in the system     new     This indicates that a notification has been entered into the system.
+2      Display to user opn     The notification has been displayed to the user. It doesn't mean that the user actually read the notification, but he/she should be aware. For that reason we consider the notification to be OPEN
+3      Remarks added   pen     Remarks have been added to the notification.
+4      Priority changed manually       pen     The priority of the notification has been changed by the user.
+5      Priority changed automatically  pen     The priority of the notification has been changed by the system. This can be the result of an action by the user or an automatical escalation.
+6      Action taken    pen     An action has been taken.
+7      Assignment to user      pen     The notification has been assigned to an user.
+8      More information or research needed.    inv     The notification is relevant and will be handled, however more information or research will be needed. For that reason the status has been altered to UNDER INVESTIGATION.
+9      Investigation completed pen     Investigation has been done. Information is available to fix the problem.
+10     Job output no longer valid      cls     By making a newer job output a valid reference, this data has been obsoleted. Since it was a reference once the output isn't interesting anymore and thus the notification can be closed.
+11     Action taken - please verify    cls     An action has been taken and things should have been resolved. Before the notification can be closed a verification has to be done. The new status is now VERIFY.
+12     Action not verified     pen     A check has been done and the results were not good. New verification is needed. The status has been changed back to PEN.
+13     Action verified cls     A check has been done and the results were approved. The notification has been closed.
+15     SMS sent        opn     An SMS has been sent.
+14     E-mail sent     opn     An e-mail has been sent.
+16     Fax sent        opn     An fax has been sent.
 17     Log entries shown       \N      The log entries relevant to the notification have been shown.
-18     Notification closed     CLS     The notification has been closed.
-19     Notification reopend    OPN     The notification has been reopend.
+18     Notification closed     cls     The notification has been closed.
+19     Notification reopend    opn     The notification has been reopend.
 \.
 
 CREATE UNIQUE INDEX action_actionid_key ON "action" USING btree (actionid);

diff --git a/src/gcm_daemon/classes/gnucomo_db_version.php b/src/gcm_daemon/classes/gnucomo_db_version.php
index ccd3703..3eb32c9 100644 (file)
--- a/src/gcm_daemon/classes/gnucomo_db_version.php
+++ b/src/gcm_daemon/classes/gnucomo_db_version.php
@@ -10,7 +10,8 @@
  //Do while statement since all updateshave to be executed starting at the 
  //latest version. It's a walk through.
 
-   switch ($active_version) {
+   switch ($active_version)
+   {
      case 1:
        //DROP the rule that prohibits updates (change of spec).
        $local_sql = "DROP RULE log_update";
@@ -197,6 +198,10 @@
       $dbms->query($local_sql);
 
 
+  case 21:
+      $local_sql = "UPDATE action SET statuscode = LOWER(statuscode)";
+      $dbms->query($local_sql);
+
 /*    
      //These columns have to be removed when a new version of PGSQL has become mainstream that supportsa DROP COLUMN
      $local_sql = "ALTER TABLE log DROP COLUMN recognized";
@@ -210,6 +215,6 @@
    $local_sql = "UPDATE db_value SET setting_value = ".$db_version." WHERE setting = 'db_version'";
 
    $dbms->query($local_sql);
-   
+
 
 ?>

diff --git a/src/gcm_daemon/gcm_daemon.php b/src/gcm_daemon/gcm_daemon.php
index e5ea247..2cc1da2 100755 (executable)
--- a/src/gcm_daemon/gcm_daemon.php
+++ b/src/gcm_daemon/gcm_daemon.php
@@ -32,7 +32,7 @@ require_once "classes/gnucomo.process_log.php";
 $project_name  = "gnucomo";    //name of the entire project
 $app_name      = "gcm_daemon"; //name of the application running
 $developrelease = "FALSE";      //Indicates if special debug settings are needed
-$db_version    = 21;           //The db_version indicates what the level of 
+$db_version    = 22;           //The db_version indicates what the level of 
                                //the database should be. If the database is 
                                //old an update will be generated.
 $gcmd_version   = 3;           //This value indicates the active version of the gcm_daemon,