Comment 8 for bug 1169569

Dan,

I'll defer to staff input on the point of NULLability. If it's the normally the case that the goal, when ordering parts, is to order them globally if a human order is ever used, then NOT NULL (as you have it) makes the most sense. If it's normally a matter of picking one and pushing it to the top (or bottom) then I think NULLABLE would be better, IMO.

Later, we'll probably want to consider a drag-and-drop UI instead of giving the user direct access to the positional value. I wouldn't call it a blocker, in any way, for this to get in, but there is other code in admin interfaces to base that on.

Thanks!