Serialize the same model twice

I am building an API from a model which gives me the following structure { "user_nucleus_id": 2, "user_id": 2, "nucleus": 2, "family_id": 2, "date": "1974-05-19T19:00:00-05:00" } But now I get the following API structure request. What I understand is that I must serialize the

Re: SMTPServerDisconnected

On 01/07/2022 08.06, Tuan Truong wrote: settings.py EMAIL_HOST ='smtp.gmail.com ' EMAIL_PORT =587 EMAIL_HOST_USER ='t...@gmail.com ' EMAIL_HOST_PASSWORD ='' EMAIL_USE_TLS =True That's really cool. Thanks a lot a lot for sharing this. Kind

Re: upgrading from 1.11 and ran into builtin permission clash

Joel Goldstick, would definitely not recommend doing an all in one update. That'd be like going from windows XP to 10 in one go. For personal projects, you could do it, but would side-eye any professional who suggested doing this with a company or workplace project.

Re: upgrading from 1.11 and ran into builtin permission clash

> What do I do about this? Clearly I should remove the permission I created. How do I deal with the migration? Should I remove the permission while I run the app as Django 1.11 before moving on to a 2.2 environment? You could rename the current view_inventorychangelog record with a data

Re: upgrading from 1.11 and ran into builtin permission clash

On Fri, Jul 1, 2022 at 8:22 AM Sheila Miguez wrote: > > Hi all, > > I'm upgrading from Django 1.11 step by step and am at the stage where I'm > upgrading to 2.2. I've run into a problem. I have a custom permission called > view_[modelname] that I created in 1.11, and that permission clashes

SMTPServerDisconnected

settings.py EMAIL_HOST = 'smtp.gmail.com' EMAIL_PORT = 587 EMAIL_HOST_USER = 't...@gmail.com' EMAIL_HOST_PASSWORD = '' EMAIL_USE_TLS = True -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving

upgrading from 1.11 and ran into builtin permission clash

Hi all, I'm upgrading from Django 1.11 step by step and am at the stage where I'm upgrading to 2.2. I've run into a problem. I have a custom permission called view_[modelname] that I created in 1.11, and that permission clashes with the default view permission that was added in 2.1.