That was a different problem.  I added a check to make sure 
'completed' was well-formed.  Committed to HEAD and FRAMEWORK_3.

The problem is that $_SESSION['import_data']['target'] is empty 
because Util::getFormData('tasklist_target') is empty.  It looks like 
the import page isn't allowing the user to choose a task list to 
import the data into.  My admin account has the "Which tasklist should 
the tasks be added to?" field, but my regular test account doesn't.

I use Nag H3 2.0.2, Horde 3.0.5 and Oracle 10g like data storage.



If one user export his tasks in a CSV o Icalendar format file and 
another user want to export this same file, the second user obtains 
this error: "DB Error: null value violates not-null constraint"



And in 'horde.log' this appears:



Oct 06 15:42:56 HORDE [error] [nag] DB Error: null value violates 
not-null constraint: INSERT INTO nag_tasks (task_owner, task_id, 
task_name, task_uid, task_desc, task_due, task_priority, 
task_completed, task_category, task_alarm) VALUES (?, ?, ?, ?, ?, ?, 
?, ?, ?, ?) [nativecode=ORA-01400: cannot insert NULL into 
("DB_USER"."NAG_TASKS"."TASK_COMPLETED")] [on line 184 of 
"/u01/horde/nag/lib/Driver/sql.php"]



I think the problem is that Oracle does not distinguish between null 
and emptiness ('') values, and several fields(task_priority, 
task_completed, task_alarm, task_private) in the table nag_tasks have 
'NOT NULL' .



Could these fields be null? Any Problems?



Greetings and thanks.



Sebastian Calero