Week ending August 11, 2019.
*Triaged:*
https://code.djangoproject.com/ticket/30674 - Autoreload fails to restart
server when exception is SyntaxError. (duplicate)
https://code.djangoproject.com/ticket/30678 - Confirm support for GDAL 3.0.
(accepted)
https://code.djangoproject.com/ticket/30680
Actually, I can think of occasions where what is displayed would vary depending
on which model the FK was from, not only on the model that is the target.
bjw
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)"
You don't need one for each field. You need one per model - similar to
__str__
On Sunday, August 11, 2019 at 3:54:03 PM UTC+2, 1337 Shadow Hacker wrote:
>
>
> Would it be possible to add a `search_display_fields` on the relevant
>> ModelAdmin, alongside `search_fields` to customise the display
>> Would it be possible to add a `search_display_fields` on the relevant
>> ModelAdmin, alongside `search_fields` to customise the display in the form
>> select box? This could be either a model field or a callable on the model or
>> modeladmin.
Another suggestion is to add
> They're not that popular actually, it seems...
They might become more popular, when they work behind proxies ... a limitation
which you usually figure out after your first important client tries to connect
from behind their corporate proxy, then you can implement polling again - a
fallback
Hi,
Lean Sensei practicing Django since 2008 here. Have tried all sorts of
strategies, the one that offers the best effort/ROI ratio is to upgrade as soon
as a new version comes out, even if that means contributing patches to
dependencies and deploying forks until patches are released.
Best
Hey can someone please have look at this ticket, I feel the requested
feature is not really feasible to implement, also it's not applicable in
the general case.
I don't think so this is feasible, this will require n(n-1)/2 comparisons
to determine whether any two of the models are swapped.
