Hello,
fishing for some ideas here. consider this scenario:
```
...
Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: /c/add/
...
Internal Server Error: /c/add/
UnboundLocalError at /c/add/
local variable 'model' referenced before assignment
...
Traceback (most recent call last):
..
charettes - Tue, 12 July 2022 at 13:11:14
> If you add fields to one your existing models the migration framework will
> add them at the end of your table as that's the most straightforward way of
> doing so. Of the top of my head only MySQL supports a syntax to add a
is it a correct takeaway,
hello there,
an interesting topic popped up on HN:
Column order in PostgreSQL does matter
https://news.ycombinator.com/item?id=32067473
I was wondering how django does this, so I looked at some of the sql
generated by migrations in my apps (particularly initial ones) and if I
read the SQL correc
Christian González - Wed, 13 May 2020 at 22:13:34
> TL;DR: Django has no (builtin/explicit) settings variable like
> PROJECT_NAME. Should have.
4 of those were comments (i wish the project templates stopped doing that)
3 of those were env variables which a deployment can override with
an actual e
Adam Johnson - Fri, 15 May 2020 at 17:53:21
> At least two of the major database servers that Django supports, PostgreSQL
> and MySQL, provide zero downgrade-ability. It's too hard for them to do.
while this is now officially true for both MariaDB and MySQL,
until recentlyish it was possible to do
hello,
i was wondering if there was any work done/planned/discussed about
implementing support for this really useful feature of libpq:
$ psql
'postgres://host1:5432,host2:5432,host3:5432/postgres?target_session_attrs=read-write'
Psycopg claims to support all dsn parameters.
https://paquier.x
