Details

      Description

      Hi

      When trying to make a survey object, you get the following error:

      Error: eZOracleDB::query()  	Mar 26 2010 10:02:03
       
      Error (1400): ORA-01400: kan ikke sette inn NULL i ("EZP"."EZSURVEY"."TITLE")
      Failed query at offset 254:
      INSERT INTO ezsurvey (title, enabled, published, persistent, one_answer, valid_from, valid_to, redirect_cancel, redirect_submit, contentobject_id, contentobjectattribute_id, contentclassattribute_id, language_code, contentobjectattribute_version) VALUES('', 1, 0, 0, 0, -1269594123, -1269594123, '/content/view/full/2', '/content/view/full/2', 58, 192, 182, 'eng-GB', 1)
       
      Start of error:
      '', 1, 0, 0, 0, -1269594123, -1269594123, '/content/view/full/2', '/content/view/full/2', 58, 192, 182, 'eng-GB', 1)
      

      Steps to reproduce

      Go thorugh ezsurvey wizard
      Create a survey object

        Issue Links

          Activity

          Hide
          Bertrand Dunogier added a comment - - edited

          In reply to comment #051322
          As said yesterday, I went by myself on testlink, and followed the TC to the letter, without reproducing the issue. I don't know what else I can do.

          Edit: tried again. Completely uninstalled ezsurvey, re-installed using the wizard, re-created several surveys, haven't seen the error.

          Show
          Bertrand Dunogier added a comment - - edited In reply to comment #051322 As said yesterday, I went by myself on testlink, and followed the TC to the letter, without reproducing the issue. I don't know what else I can do. Edit: tried again. Completely uninstalled ezsurvey, re-installed using the wizard, re-created several surveys, haven't seen the error.
          Hide
          Bertrand Dunogier added a comment -

          Okay, we have new data.

          This error comes from the way the ezsurvey tables are created. The TC says it is done using the survey wizard. It is NOT. If it was, this error would not occur.

          The wizard uses the db_schema.dba file, with custom oracle settings from settings/dbschema.ini.append.php. In these settings, there is one that says that ezsurvey.title CAN be null, while the common schema file says it can't. The reason is that Oracle interprets NULL & empty string the same way.

          I have understood after talking to the QA team that unlike what the TC says, the test system creates the tables differently.

          As far as I'm concerned, the bug is invalid.

          Show
          Bertrand Dunogier added a comment - Okay, we have new data. This error comes from the way the ezsurvey tables are created. The TC says it is done using the survey wizard. It is NOT. If it was, this error would not occur. The wizard uses the db_schema.dba file, with custom oracle settings from settings/dbschema.ini.append.php. In these settings, there is one that says that ezsurvey.title CAN be null, while the common schema file says it can't. The reason is that Oracle interprets NULL & empty string the same way. I have understood after talking to the QA team that unlike what the TC says, the test system creates the tables differently. As far as I'm concerned, the bug is invalid.
          Hide
          Vidar Langseid added a comment -

          I have now fixed so that the testsystem do not try to insert the schema without the ezsurvey extension being activated. Instead, the schema is also imported by the wizard from now on

          Show
          Vidar Langseid added a comment - I have now fixed so that the testsystem do not try to insert the schema without the ezsurvey extension being activated. Instead, the schema is also imported by the wizard from now on
          Hide
          Gaetano Giunta added a comment -

          Btw, if you look at the extension sql sources, you have an oracle version too. And the tile field is nullable in that file.
          So using the mysql version for that sql script / part of db definition is just wrong.

          Show
          Gaetano Giunta added a comment - Btw, if you look at the extension sql sources, you have an oracle version too. And the tile field is nullable in that file. So using the mysql version for that sql script / part of db definition is just wrong.
          Hide
          Geir Arne Waaler added a comment -

          Not reproducable, original issue is fixed. I move it to Closed.

          Show
          Geir Arne Waaler added a comment - Not reproducable, original issue is fixed. I move it to Closed.

            People

            • Assignee:
              Bertrand Dunogier
              Reporter:
              Vidar Langseid
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: