I have some plans (see https://github.com/django/deps/pull/6) to rework
more widely how indexes are managed and allow finer control over them. It
pretty much includes all the things mentioned by Alex. I'm intending on
doing some work on it over the next few weeks.
Marc
On 20 March 2015 at 02:27,
I agree that this is a problem, and I'd like to see more control over
indexes generally in Django.
However, at first glance I suspect that fixing only your problem would mean
adding special-case gunk to the Field class in addition to the Postgres
schema editor where it currently lives[1]. It fe
django-flat-theme is available on pypi
now: https://pypi.python.org/pypi/django-flat-theme
On Wednesday, 18 March 2015 23:53:04 UTC+5, elky wrote:
>
> Yeah, I'm planning to publish this app on pypi this week
>
>
--
You received this message because you are subscribed to the Google Groups
"Djan
There's been some recent discussion in a django-users thread[1] about
the impending end-of-life of Django 1.6, which in turn will mean
end-of-life for Django supported on Python 2.6. In addition, the
end-of-life of the current LTS release, Django 1.4, will mean
end-of-life for Django supported on P
As proposed by timgraham in https://code.djangoproject.com/ticket/24507 I
open the discussion here.
When adding db_index=True on a CharField Django automatically create 2
indexes on some backends as PostgreSQL. But in usage the second index is
not always necessary if you never use contains() or
I believe you are asking for a template tag to handle Flash content better.
Tell me if I am wrong but it sounds like a good candidate for a third party
app. I don't think it belongs in Django as a Django contribution.
On Wednesday, March 18, 2015 at 5:06:58 PM UTC-4, Debesh Mohanty wrote:
>
> He
Ticket and patch have been submitted regarding this:
https://code.djangoproject.com/ticket/24496
https://github.com/django/django/pull/4337
Since this is related to CSRF and technically weakening the strictness of
the Referer check, Tim Graham suggested soliciting feedback here to get
more eyeb
I am not really sure what exactly you are proposing here, but Flash is on
its way to die and that is good. I really don't see why Django should add
any support for Flash, that said you are obviously free to write your own
template tags to get rid of some boilerplate code.
Cheers,
Florian
On We