Slicing results assigns wrong values to fields

[kaselis]

Whenever I try to get other than the first object from DB, my object fields are shifted by one, and the last one is completely discarded. For example if I have this model:

class Person(models.Model):
    uuid = models.CharField(max_length=36, primary_key=True)
    title = models.CharField(max_length=10)
    first_name = models.CharField(max_length=50)
    last_name = models.CharField(max_length=50)

and then if I try to fetch an object with this code

Person.objects.all()[1]

my object going to have these values assigned:

uuid = 2L
title = uuid
first_name = title
last_name = first_name

and the last_name value is discarded completely. I tracked down the issue to the generated query:

sql = "SELECT {row_num_col}, {outer} FROM ( SELECT ROW_NUMBER() OVER ( ORDER BY {order}) as {row_num_col}, {inner}) as QQQ where {where}"

and the cause is the selection of {row_num_col} column, which is not needed for the output. It works fine for the first object, because different query is issued. I'm using django==1.8, but I don't think it matters, there is simply no reason to select that field for the output.

[kaselis]

It seems there was a change in django how it converts database-python types and because of that, resolve_columns is no longer called in django 1.8:

django/django@e910340

[eskhool]

Facing the same issue...@kaselis did you find a resolution for the same?