Yes it worked well enough for over then it should be.
So yes i would love to give it a try.
So we will be storing json as string in the database? or what would be the
recommended path to go about this ?!
On Wednesday, August 26, 2015 at 3:34:31 PM UTC+2, Tim Graham wrote:
>
> The current
On Wednesday, August 26, 2015 at 9:08:16 AM UTC+2, Florian Apolloner wrote:
>
> Ups, not enough coffee yet, the admin.ready() just registers the checks,
> it does not execute them, so order should not matter -- I shall close my
> browser now and get some coffee :D
>
I don't know how exactly
The patch allowing F objects for select_related and prefetch_related
methods was trivial, unfortunately F uses "name" field as a part of
Expression interface, so dotted querying will conflict with internal field
(as "name" is quite a popular name for model field).
>>> Contains(F.user.name,
The current approach has worked "well enough" for 10 years. I think we can
wait a little longer for a better solution rather than change the message
format twice. Want to give it a try?
On Tuesday, August 25, 2015 at 11:07:45 AM UTC-4, Ramez Ashraf wrote:
>
> Dear devs
> I'm the PR mentioned
Hello all,
I am still waiting for some information about what should I do next to get
this pulled into Django. Isn't here somebody willing to take a look at this?
PR is at https://github.com/django/django/pull/5108
--
You received this message because you are subscribed to the Google Groups
Ups, not enough coffee yet, the admin.ready() just registers the checks, it
does not execute them, so order should not matter -- I shall close my
browser now and get some coffee :D
On Wednesday, August 26, 2015 at 9:07:15 AM UTC+2, Florian Apolloner wrote:
>
> I think the fix for you currently
I think the fix for you currently is to put __your__ app before the admin
app, this way your ready() will patch the user first and then the admin
checks run.
On Wednesday, August 26, 2015 at 9:06:07 AM UTC+2, Florian Apolloner wrote:
>
>
>
> On Tuesday, August 25, 2015 at 6:19:44 PM UTC+2,
On Tuesday, August 25, 2015 at 6:19:44 PM UTC+2, Marcin Nowak wrote:
>
> Thanks, Carl. This specific error can solved by changing
> 'django.contrib.admin' to 'django.contrib.admin.apps.SimpleAdminConfig' in
> INSTALLED_APPS.
>
This disables admin autodiscovery though, I doubt that is what you