Support Forum

[mdurant]

We're running into a problem adding new issues to a project that we've been successfully using for a couple of months now. Whenever we enter Name and Category now and click 'Add,' we're getting this message:

ERROR: ExecInsert: Fail to add null value in not null attribute task_resolution
Please press Back and try again...

We did just recently (Monday or Tuesday of this week) upgrade from the 2.7 beta to the latest you had on the site, so it looks like a consequence of that. Any thoughts? We need this working again as quickly as possible.

Thanks!
Mark

[admin]

We're running into a problem adding new issues to a project that we've been successfully using for a couple of months now. Whenever we enter Name and Category now and click 'Add,' we're getting this message:

ERROR: ExecInsert: Fail to add null value in not null attribute task_resolution
Please press Back and try again...

We did just recently (Monday or Tuesday of this week) upgrade from the 2.7 beta to the latest you had on the site, so it looks like a consequence of that. Any thoughts? We need this working again as quickly as possible.

Thanks!
Mark

This is because in 2.7 release field task_resolution in table gr_task should allow null (it is "not null" in 2.7 beta).

You should SQL execute script like this (for ORACLE):

Code: Select all

ALTER TABLE gr_task DROP  CONSTRAINT ftask_3;

ALTER TABLE gr_task
       ADD  (   task_temp VARCHAR2(32)  );

UPDATE gr_task set task_temp=task_resolution;

ALTER TABLE gr_task
       DROP  (   task_resolution );

ALTER TABLE gr_task
       ADD  (   task_resolution VARCHAR2(32)  );

UPDATE gr_task set task_resolution=task_temp;

ALTER TABLE gr_task
       DROP  (   task_temp  );

CREATE INDEX itask_6 ON gr_task
(
        task_resolution
);

ALTER TABLE gr_task
       ADD  ( CONSTRAINT ftask_3
              FOREIGN KEY (task_resolution)
                             REFERENCES gr_resolution (resolution_id) ) ;



If you use other DBMS - just let me know.

PS. I suggest avoid use alpha/beta versions in production environment.

[mdurant]

We're using Postgre SQL ... if you could send the SQL for that, we should be in good shape. Thanks!

(We're not, strictly speaking, in a production environment ... but your point's well taken. )

[admin]

We're using Postgre SQL ... if you could send the SQL for that, we should be in good shape. Thanks!

Its very similar:

Code: Select all

ALTER TABLE gr_task DROP  CONSTRAINT ftask_3;

ALTER TABLE gr_task
       ADD     task_temp VARCHAR(32)  ;

UPDATE gr_task set task_temp=task_resolution;

ALTER TABLE gr_task
       DROP     task_resolution ;

ALTER TABLE gr_task
       ADD     task_resolution VARCHAR(32)  ;

UPDATE gr_task set task_resolution=task_temp;

ALTER TABLE gr_task
       DROP     task_temp  ;

CREATE INDEX itask_6 ON gr_task
(
        task_resolution
);

ALTER TABLE gr_task
       ADD   CONSTRAINT ftask_3
              FOREIGN KEY (task_resolution)
                             REFERENCES gr_resolution (resolution_id)  ;