Howdy Viktor, On Feb 1, 1:36 pm, Viktor <viktor.n...@gmail.com> wrote: > Hi, > > did you got any response or did you managed to solve your problem? > I've just started to search for a UUIDField, and it would be great to > have proper uuid columns for postgres. > > If so do you plan to commit it to django_extensions?
Sorry for the delayed reply. I just noticed your message. I do have my custom uuid field working, using native uuid datatype with postgresql and char field for other databases. There is one situation where I'm seeing a problem in the Django admin interface and as soon as I can resolve it I will post the complete solution. The problem is seen when using a model that has a uuid primary key that is edited inline (tabular or stacked) on the same page as a parent model. I see this problem not just with my version of UUIDField but also with the one that is currently in django- extensions. I'm trying to figure out what Django does differently when using it's own automatically generated primary key as opposed to using a declared primary key. That is the only situation I have found that causes a problem. There is no difficulty with the admin interface when working with models that have uuid primary keys when they have their own admin edit page. --gordon --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
