Re: How to filter choices in Django2's autocomplete_fields?

2018-08-29 Thread ciaran . courtney
Not possible ATM it seems, pity https://code.djangoproject.com/ticket/29010 -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: How to filter choices in Django2's autocomplete_fields?

2018-08-29 Thread ciaran . courtney
You need to override ModelAdmin.get_search_results() as per https://docs.djangoproject.com/en/2.1/ref/contrib/admin/#django.contrib.admin.ModelAdmin.autocomplete_fields My problem is I override ForeignKeyField in AdminForm, where I can filter based on self.instance, this is not possible in

Re: Docs on multiple servers/memcached daemons not clear

2018-08-07 Thread ciaran . courtney
Sorry for double post, didn't realize there was an approval step https://groups.google.com/forum/#!topic/django-users/EZho7Y8KSOw -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it,

Docs on multiple servers/memcached daemons not clear

2018-08-07 Thread ciaran . courtney
https://docs.djangoproject.com/en/2.1/topics/cache/#memcached When running a memcached daemon on each server, is it implicitly implied that each memcached daemon should be configured to listen on 0.0.0.0 (default is 127.0.0.1) so that all Django processes can get/set in one big memory pool,

Docs on distributed memcached setup are not clear

2018-08-07 Thread ciaran . courtney
https://docs.djangoproject.com/en/2.1/topics/cache/#memcached Particularly the multiple servers section, which does not detail if all memcached daemons should be configured to listen on all interfaces i.e. 0.0.0.0 So just as a sanity check: Scenario 1: (memcached installed naively ( i.e.