
|
If you were logged in you would be able to see more operations.
|
Google issue summary
|
|
|
|
Time Tracking:
|
|
Original Estimate:
|
2 hours
|
|
|
Remaining Estimate:
|
2 hours
|
|
|
Time Spent:
|
Not Specified
|
|
|
|
| Resolution Date: |
03/10/07 13:39
|
| Require Callback: |
No
|
| Participants: |
Florent Guillaume
|
| Tags: |
|
|
When a hierarchical directory has an entry with id=A and parent=P, and another entry with id=A and parent=Q, then deleting one entry deletes both.
This is because internally directory ids are supposed to uniquely identify the entry, and the case of a multi-column primary key was not considered. Only the id is taken into account in the SQL delete statement. (I haven't checked LDAP yet.)
|
|
Description
|
When a hierarchical directory has an entry with id=A and parent=P, and another entry with id=A and parent=Q, then deleting one entry deletes both.
This is because internally directory ids are supposed to uniquely identify the entry, and the case of a multi-column primary key was not considered. Only the id is taken into account in the SQL delete statement. (I haven't checked LDAP yet.)
|
Show » |
|
Ideally all the directories should be refactored to allow a multi-value primary key, but that's way more complex.