Yes, there's an open ticket for that:
https://code.djangoproject.com/ticket/17881
On Sunday, July 12, 2015 at 2:18:24 PM UTC-4, damon c wrote:
>
> The default behavior for the modelAdmin is to render a element
> containing *every* instance of the model referred to by the FK.
>
> When this fie
>From http://www.postgresql.org/docs/9.4/static/sql-createtable.html
UNLOGGED
If specified, the table is created as an unlogged table. Data
written to unlogged tables is not written to the write-ahead log (see
Chapter 29), which makes them considerably faster than ordinary
tables. However
The default behavior for the modelAdmin is to render a element
containing *every* instance of the model referred to by the FK.
When this field refers to a model that has for example, 100,000 or more
entries, this can have the affect of crashing a server, a browser, or at
best making new user
I just ran into this ticket:
https://code.djangoproject.com/ticket/24306
I found myself in a situation where it would be really useful.
Two questions:
- has anybody verified that UNLOGGED tables really perform faster when
running tests with Postgres?
- is this feature on the TODO list
+1
On 12 July 2015 at 15:53, James Bennett wrote:
> There's not much to this, really, except what's in the subject line of
> this message.
>
> The problem of providing a single-file, no-build-step format for
> distributing and installing Python packages has been solved by wheels, and
> wheels al
There's not much to this, really, except what's in the subject line of this
message.
The problem of providing a single-file, no-build-step format for
distributing and installing Python packages has been solved by wheels, and
wheels also don't cause the pile of weirdness that comes with using eggs.
