You could also make a custom uuid field that handles this. Use a uuid subclass that uses base 58 for string conversion. And then convert to correct database representation in the field methods
On Fri, Aug 24, 2018, 9:13 AM Chris Foresman <fores...@gmail.com> wrote: > It almost sounds like you'd need to patch Django's URL resolver to look > for capture groups that might be a primary key, and then base58 decode the > value before passing it as a value to the view method being called. Then > you would need to write your own function, `my_reverse`, which would look > for kwargs that would be primary keys, and base58 encode them before > passing them on to reverse and then returning that. > > -- > You received this message because you are subscribed to the Google Groups > "Django REST framework" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-rest-framework+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django REST framework" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-rest-framework+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
