My favorites | Sign in
Project Home Source
READ-ONLY: This project has been archived. For more information see this post.
Search
for
  Advanced search   Search tips   Subscriptions
Issue 19: Cannot easily delete supervisors
1 person starred this issue and may be notified of changes. Back to list
 
Project Member Reported by dmbs...@gmail.com, Oct 15, 2010
When deleting a supervisor, it ask to delete a student (which is generally not allowed). Thus it becomes confusing why supervisors cannot be deleted. To make matters worse the primary supervisor field is a filtered foreign key field. When the student's placement changes it will appear to be blank, when it is actually linked to an outdated supervisor.

http://code.djangoproject.com/ticket/6108

Until Django handles this better a work around must be issued. Since sugarcrm uses a Never delete, just mark as deleted approach this may be the best option. "Deleting" a supervisor will simply null out any references to them while keeping them.
Oct 15, 2010
Project Member #1 dmbs...@gmail.com
http://code.djangoproject.com/ticket/6870 is a related bug that with a fix that looks promising. Hopefully this will make it into Django 1.3 in early 2011.

Until then SWORD will null out primary supervisor for any student when deleting the supervisor. This will happen after the warning so it looks like the user is about to delete a student! It's not ideal but it will work while we wait for Django 1.3.
Status: Started
Labels: -Priority-High -Usability Priority-Medium
Nov 3, 2010
Project Member #2 dmbs...@gmail.com
(No comment was entered for this change.)
Labels: Component-work_study Milestone-Release2.0
Mar 25, 2011
Project Member #3 dmbs...@gmail.com
Uses django 1.3 on_delete to null out links.
Cc: -jdiaz%cr...@gtempaccount.com
Mar 25, 2011
Project Member #4 dmbs...@gmail.com
(No comment was entered for this change.)
Status: Fixed

Powered by Google Project Hosting