Does not respect relationships

@iStryker, here's an example how it can be reproduced:

• Create a view displaying nodes.
• Add node author relationship to the view.
• Add aggregation for node title so that the view displays number of nodes for each user (so that we have a single row per user).
• Add a user draggableviews sorting and field and select it to work for the node author relationship (i.e. now we can sort the users by dragging).
• Check the resulting draggableviews form HTML and see that the rows IDs are NIDs, not UIDs.
• Make sure that the reordering and clicking "Save" doesn't actually save the order.
• Apply the patch and make sure that the IDs now are UIDs, and the order saving now works.

It's not exactly the case I had a problem with, but probably it's the easiest way to reproduce the issue.

@iStryker apparently I was not clear enough. From what you describe looks all your nodes had the same author. If so, the described behaviour is the correct one: when you sort authors and there is a single author, only one record is created.

I mentioned there must be aggregation enabled in the view with counting number of nodes per author, so that you have a single line per author.