Re: [admin] submit_row template tag reusability issue

Updated the ticket and sent a PR, I report the comment here too for convenience: Just opened PR https://github.com/django/django/pull/6078. A more paranoid test could be written, like creating a custom app with an admin that extends the context, loads a modified version of the subimt_row templ

Re: Admin Improvement - Autocomplete & improved search for FKs

Here is an accepted ticket for autocomplete: https://code.djangoproject.com/ticket/14370 The "improved search" seems like what we already have when using raw_id_fields so it seems like it should be easy to include as part of the autocomplete UI. I don't see think it needs to be a separate optio

Re: Admin Improvement - Autocomplete & improved search for FKs

Nice, I guess my google skills are quite bad since I looked for it and didn't find it :) Opened 5 years ago with progress but still not completed, looks like it may need some help El miércoles, 3 de febrero de 2016, 9:13:54 (UTC-3), Tim Graham escribió: > > Here is an accepted ticket for autoco

#25897 - managers defined on non-abstract base classes inherited by child classes

Hi. According to documentation managers defined on non-abstract base classes are not inherited by child classes. In fact they're inherited via python MRO. I made pull request

Re: Bank of examples.

You might also want to check out https://djangosnippets.org though I'm sure that many of these examples are before 1.9 On Wednesday, 13 January 2016 08:30:06 UTC-6, Parki wrote: > > I've just started out to learn Django and I realize how great would be if > we had a bank of Django examples. > I

Re: #26165 new Cleanup/optimization wanted to start with a documentation ticket

Hi. I have compiled a list of questions. I made a section in the faq folder. These are the questions and answers I wrote. These answers were written based on the thread referenced on the ticket FAQ: CSRF Protection = Is Django's CSRF protection vulnerable? --

Re: #26165 new Cleanup/optimization wanted to start with a documentation ticket

Please send the pull request -- we do review there, not on this mailing list. Thanks! On Wednesday, February 3, 2016 at 10:27:32 AM UTC-5, Vivek unni wrote: > > Hi. I have compiled a list of questions. I made a section in the faq > folder. These are the questions and answers I wrote. These answe

Re: #25897 - managers defined on non-abstract base classes inherited by child classes

Could this go through a deprecation where any use of the inherited managers to be removed will raise a warning for a couple releases? If anyone is relying on the behavior, they just need to add the managers to any subclasses, correct? On Wednesday, February 3, 2016 at 9:16:41 AM UTC-5, Alex Pol

Re: Remove null assingment check for non-nullable fields?

On Wednesday, February 3, 2016 at 12:26:26 AM UTC+1, Tim Graham wrote: > > There's a proposal to remove this behavior: > > > >>> obj.fk = None > ValueError('Cannot assign None: "Obj.fk" does not allow null values.) > Yes please, if you do IntegerField(null=False) you can still do instance.xxx = N

Re: Replacing the contrib.sites Site model with a setting?

What would be the recommendation for assigning content to a particular site in a shared DB model? Integer field with the current SITE_ID to create a sort of faux FK or M2M? Choices? One thing I like about this pattern I haven't seen discussed already is that it would make it far easier to exten

Re: #26165 new Cleanup/optimization wanted to start with a documentation ticket

Thanks for helping me out. Sorry for the mess up regarding the Triage stage. Thanks for walking me through the whole process. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this grou

Re: remove support for unsalted password hashers?

Acknowledged Donald, I just didn't want to bite off too much at once. I think the unsalted hashers removal could be done as a backwards-incompatible change. I wrote up some documentation including queries to check if your database is affected: https://github.com/django/django/pull/6082 I'll be

Re: Remove null assingment check for non-nullable fields?

You're probably think of the change in 1.8.4 that moved the unsaved model instance assignment data loss check (added in Django 1.8) to Model.save() to allow easier usage of in-memory models (#25160 ). The checks in question have been in Django since

Re: Feature proposal: selection of views and tables for inspectdb

Sorry I've been pretty disconnected from this thread. The TL;DR version of the current situation is as follows: in Oracle, if a user has read access to tables/views not owned by him, those are not listed by the inspection mechanism inspectdb uses, so no model is generated for them. They can be

Re: Query on BooleanField with values other than True and False, bug or intentional?

I don't think that's the same thing. We're talking about interfacing with a system that has clearly delineated values. > The boolean type can have several states: "true", "false", and a third > state, "unknown", which is represented by the SQL null value.[1] While the database accepts a variet

Re: Query on BooleanField with values other than True and False, bug or intentional?

I'm with Tim here - we shouldn't alter the behavior at this point. On Thu, Feb 4, 2016 at 8:17 AM, Chris Foresman wrote: > I don't think that's the same thing. We're talking about interfacing with a > system that has clearly delineated values. >> >> The boolean type can have several states: "true