As it always happens, 4am Sunday it well went to hell – Django create two instances of ‘2021-08-15’.
Eventually every requests that had this line in it just crashed.
Why did this happen? Well, apparently two instances are not supposed to be made.
My friends and I came to a conclusion that with a very high amount of requests Django missed that tiny bit of time between executing get_or_create method and actually writing an instance to PostgreSQL.
Well good thing - I went to bed late, and my team woke me up much earlier than I would wake up.
What is he solution? If the field is meant to be unique, make it unique:
date = DateField(unique=True)
Following Channels’ docs I encountered yet another error the solution to what was not obvious right off the bat.
This was my original post in October 2020 and I stand by it.
You can make your project work with Google Firebase - it handles signals well enough. Yes it is primarily used by mobile developers, but overall it is fine for web too.
I spent trying to install Django Channels on my local Linux 18.04, and I kind of made it work, but then I had to deploy it... And as a professional backender you don't want to let people down.
I decided to try Channels because my Python-related friends talked about it. But days into the trouble I asked my friend about a certain step and he asked me in return "oh so [you use it because] they fixed Channels since two years ago?". I as like ??????????????????. So that moment I ditched it. Too much time wasted, but I like the result I achieved with Firebase.
What I am saying - Firebase is fast and universal. In a matter of days I managed to make and deploy an internal Customer Support chat service that connected mobile app users and a support from the web.</p>
I will be writing a new series on Django + Firebase, and this post is pretty much a short introduction.
Froala provides a great WYSIWYG editor for Django admin, but on page the styles for django-froala-editor didn’t work no matter what I tried. It didn’t look like what I get at all.
At some point, it was clear that providing a quick fix would suffice. I made a short style sheet to make these styles work on Django templates. It is my example that fits my needs. I don’t eliminate the fact that I failed to find an organic solution to this via package files.
You ran makemigrations, then migrate and yet Django dares to throw an error? Incomparable betrayal! Let’s look through several cases.
For ages encountering migrations errors, I have been wipin the entire database and migrations files. Until one day an error occurred at a production server. There was no other option but to calm down and learn how to fix it.
I am starting the Careless Development series where I post a little issue that started as a problem solving and ended up being an oversight issue. Utter disappointment! It took me some time to inspect Pycharm inside and out, so here it is.
I should say that the bigger the project, the more it happens. But enough of self-justification.