(maybe optionally) create "missing" objects on POSKeyError

Registered by Jim Fulton on 2009-08-22

Now, a POSKeyError (which shouldn't happen :) causes a failure to load teh referring object. Maybe instead (maybe optionally) create a special object for the missing objects, much as we do for broken objects. The missing object should be immutable and it should be impossible to save an object that has a reference to a missing object.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.