There are valid reasons for not using an ORM but the points made in this article are plain false. >“Roughly” because Django ORM doesn’t support the JSONB `?` operator. The `has_key`…
TIL I wasn't aware MySQL functional indices were implemented using virtual columns [0] [0] https://dev.mysql.com/doc/refman/8.4/en/create-index.html#cr...
Virtual generated columns are not required to allow an index to be used in this case without incurring the cost of materializing `to_tsvector('english', message)`. Postgres supports indexing expressions and the query…
Small heads up that the application link in the job description pointing at https://opencraft.com/jobs/open-source-developer/ leads to a 404.
There is an ongoing effort to include back the equivalent in core [here](https://github.com/django/django/pull/17554)
It doesn't make the article less interesting but this statement is wrong most of the time > This scenario is essentially identical to one in which there's a single migration statement that requires an…
There are valid reasons for not using an ORM but the points made in this article are plain false. >“Roughly” because Django ORM doesn’t support the JSONB `?` operator. The `has_key`…
TIL I wasn't aware MySQL functional indices were implemented using virtual columns [0] [0] https://dev.mysql.com/doc/refman/8.4/en/create-index.html#cr...
Virtual generated columns are not required to allow an index to be used in this case without incurring the cost of materializing `to_tsvector('english', message)`. Postgres supports indexing expressions and the query…
Small heads up that the application link in the job description pointing at https://opencraft.com/jobs/open-source-developer/ leads to a 404.
There is an ongoing effort to include back the equivalent in core [here](https://github.com/django/django/pull/17554)
It doesn't make the article less interesting but this statement is wrong most of the time > This scenario is essentially identical to one in which there's a single migration statement that requires an…