Hi Mike,
Thanks for the reply. For future reference, it was pointed out to me that I
missed both an explicit note in the documentation [1] and an issue tracking
a potential change in the future [2].
Do you have any suggestions as to the actual SQL migration which needs to
be applied for postgr
this is a big part of what DRF brings to the table that "traditional"
django doesn't have.
https://www.django-rest-framework.org/api-guide/relations/
On Sunday, May 15, 2022 at 4:05:02 PM UTC-4 954i...@gmail.com wrote:
> It's too inconvenient to paste the code in the email, I'll just copy a
It's too inconvenient to paste the code in the email, I'll just copy a
StackOverFlow link.
https://stackoverflow.com/questions/72251670/how-to-construct-nested-queryset-with-django-orm
Ignoring the `DRF` part, I want to construct an `object` like this, how to
do it?
--
You received this messa
I hosted a Django project on Name Cheap, it works well on development, but
on going live I noticed image creation and update is not working
here is the error I'm getting! Please kindly help
ImportError at /admin/store/otherimages/2/change/
/lib64/libc.so.6: version `GLIBC_2.14' not found (require
On 14/05/2022 11:44 pm, Jeremy Lainé wrote:
Hi!
I'm currently looking at how to migrate all my models from AutoField
to BigAutoField. For all the explicitly defined models the process
seems pretty straightforward:
* change DEFAULT_AUTO_FIELD to BigAutoField
* generate migrations
* appl
5 matches
Mail list logo