[Savannah-dev] [Bug #14] Rows id 100 not reserved in SF database (was: default task dep = https & phpgroupware)

[noreply]

Bug #14, was updated on 2002-Apr-20 12:00
Here is a current snapshot of the bug.

Project: savannah
Category:  Database
Severity:  7
Priority:  Immediate
Bug Group:  None
Resolution:  None
Assigned to:  ljulliar
Status:  Closed
Effort:  3.00
Summary:  Rows id 100 not reserved in SF database (was: default task dep = 
https & phpgroupware)

Original Submission:  When no dependant task is entered for a task, a task
with synopsis "Sysadmin: https & phpgroupware" is listed.

https://savannah.gnu.org/pm/task.php?func=detailtask&project_task_id=403&grou
p_id=482&group_project_id=153

Note: as an admin of this project, I only see this when
I'm not logged in.


Follow-Ups:
**********

-------------------------------------------------------
Date: 2002-Apr-20 22:13
By: ljulliar

Comment:
I thnik I have modified all the necessary tables. That is to 
say:forum_group_list, patch, patch_history, project_task, project_history, 
support, group.

Wherever necessary I introduced the reserved id #100 and assign it to group 
#100 (none). Since group 100 was already defined (project "miscfiles") I 
changed it to 1875 after getting the green light from the owner. I don't think 
there is anything to change on the backend side for this group.

Rk: the user table already had id 100 reserved.

-------------------------------------------------------
Date: 2002-Apr-20 14:08
By: ljulliar

Comment:
This is a problem I was sure the Savannah team overlooked :-) I had the exact 
same one on CodeX at Xerox. The task you see has the task_id at 100, and 100 is 
a very specific value in almost all SourceForge tables. It means "None" or 
undefined.

In other words the value 100  should be reserved in all tables and if I 
remember correctly the SQL provided by SF did not initialize the table 
correctly.

SO it means that we must change the entry 100 in taks, bug, groups, etc... 
everywhere or the system won't work correctly. it can even lead to data 
corruption in some cases. I'll look into this and make the necessary 
modifications in the database. I will also warn the projects  to whihc item 
number 100 has been assigned that this item number is going to be changed to a 
new one.



For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=14&group_id=11