Thanks for the answer.
What do you suggest to use instead of this ugly method, raw sql?
суббота, 14 ноября 2015 г., 17:59:51 UTC+3 пользователь Tim Graham написал:
>
> I'm not sure that type of monkeypatching of Model._meta.db_table is meant
> to be supported. You could try to bisect Django's com
Thanks for the answer.
What do you suggest to use instead of this ugly method, raw sql?
--
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 django-users+unsubscr...@
>
>
> By default, Django’s admin uses a select-box interface () for
> fields that are ForeignKey. Sometimes you don’t want to incur the
> overhead of having to select all the related instances to display in the
> drop-down.
>
Thanks a lot - that was what it was all about; Django tried to popul
On Sun, Nov 15, 2015 at 12:04 AM, wrote:
> Thanks for the answer.
> What do you suggest to use instead of this ugly method, raw sql?
>
Would it make sense to serialize a ModelDatabaseA object (perhaps into JSON
or a standard Python dict) and use that to populate/create a ModelDatabaseB
object, s
I've been trying to figure out why I can't delete child records
displayed in the Admin. Finally tracked it down to this method in
admin.py which when commented out restores the ability to check the
Delete box and get rid of the child record on clicking Save.
def save_formset(self, request, for
On 16/11/2015 4:32 PM, Mike Dewhirst wrote:
I've been trying to figure out why I can't delete child records
displayed in the Admin. Finally tracked it down to this method in
admin.py which when commented out restores the ability to check the
Delete box and get rid of the child record on clicking
6 matches
Mail list logo
