Sorry to have dropped out for a few days there. James, when I said I only have this one I should clarify. I had 90 records I wanted to put into one model, and 1 record to put into another. The 1 record is linked to by a fk from the other 90. For whatever reason, I was able to put the single record fixture in without issue. Once I started having trouble with the others, one of the many things I tried was taking all uuid's out to see if that helped, and of course it didn't. So at one time the only uuid in the fixture was the fk link to the model with only a single record in it. That didn't work either.
All my pks at this moment are uuids. I read the SO link. I hope this does not come across as too naive, but how would I check this as that person did? Is it as simple as asking the shell what the uuid of x is, or is there more to it because it might report back a uuid even though there is some other 'ghost' integer floating around as well? On Fri, Feb 19, 2016 at 1:36 PM, James Schneider <jrschneide...@gmail.com> wrote: > The only uuid currently in this fixture is the one I got from Django when >> I put another model (only one row) in with a fixture (no date field) and it >> worked. I needed the uuid of that object to put into the foreign key of the >> model I am having trouble with now. >> >> >> > So I was sniffing around the Internet for ideas, and I came across this > SO: > http://stackoverflow.com/questions/32445546/django-uuidfield-modelfield-causes-error-in-django-admin-badly-formed-hexadecim > > You mentioned that this is the only UUID in your fixture (which seems > strange). Do you have a mixture of UUID's and integer PK's? It's possible > that the UUID errors are actually resulting from an integer being passed to > uuid.UUID() rather than one of your real UUID's. > > -James > > > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Django users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/django-users/Q4zybgExDyY/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > django-users+unsubscr...@googlegroups.com. > To post to this group, send email to django-users@googlegroups.com. > Visit this group at https://groups.google.com/group/django-users. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/CA%2Be%2BciX%3Dz0KEvJJdMF7%3D3MKrWsuvhO6P%2B6%2BRso_QYM4Y6%3D4gsA%40mail.gmail.com > <https://groups.google.com/d/msgid/django-users/CA%2Be%2BciX%3Dz0KEvJJdMF7%3D3MKrWsuvhO6P%2B6%2BRso_QYM4Y6%3D4gsA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAKd6oBzJ_M%3Dz94whvuLsUD6xOz%3DCQLMDQwtAgC8iGB%3DZOoH5Kg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
