Hi,
On 26.07.2016 04:28, akki wrote:
* Fixed #24442 <http://code.djangoproject.com/ticket/24442> -
Improved schema's index name creating algorithm
Updated !6898 <http://github.com/django/django/pull/6898> to take
all column names into account while creating index name
* Add support for column ordering (ASC/DESC) in class based indexes
Somewhat provides the feature requested in #20888
<https://code.djangoproject.com/ticket/20888#comment:10>
WIP code on my branch -
https://github.com/akki/django/commits/gsoc-indexes-order
Modifying introspection of all databases to return column order as
well (required for testing) -- implementation for Oracle remaining.
If you get stuck with Oracle I can lend a hand to help to figure out the
details.
* Implement Hash index class
WIP implementation at
https://github.com/akki/django/commits/gsoc-indexes-hash
Currently implemented only for postgresql because that's the only
backend which fully supports it AFAIK (MySQL supports for some
storage engines but neither for MyISAM nor InnoDB).
On Tuesday, 19 July 2016 10:41:16 UTC+5:30, akki wrote:
* Introduce Meta.indexes
PR - https://github.com/django/django/pull/6857
<https://github.com/django/django/pull/6857>.
Ticket - https://code.djangoproject.com/ticket/26808
<https://code.djangoproject.com/ticket/26808>.
Made a design change so that index can drop it's model
attribute by introducing /Index.set_name_with_model/ method
Wrote some left out tests for /related_dependencies/.
* Fixed #24442 <https://code.djangoproject.com/ticket/24442> -
Improve schema's index name creating algorithm
PR - https://github.com/django/django/pull/6898
<https://github.com/django/django/pull/6866>
Updated according to reviews and suggestions.
* Resolved bug when unique_together was dropped along with it's
field
PR - https://github.com/django/django/pull/6926
<https://github.com/django/django/pull/6926>.
Initially wrote a temporary fix (which left out some other
corner cases) to the problem (afterwards I realised the better
fix and sent PR).
Other comments about the issue on the ticket -
https://code.djangoproject.com/ticket/26180
<https://code.djangoproject.com/ticket/26180>.
Resolved a similar issue that had crept up for Meta.indexes -
updated !6857 <https://github.com/django/django/pull/6926>
accordingly.
On Tuesday, 12 July 2016 14:17:21 UTC+5:30, akki wrote:
* Restructure index migrations - Polished according to all
reviews, the PR
<https://github.com/django/django/pull/6866> has been merged.
* Introduce Meta.indexes - Updated PR
<https://github.com/django/django/pull/6857> according to
suggestions as per reviews.
* Improve schema's index name creating algorithm - #24442
<https://code.djangoproject.com/ticket/24442>!6898
<https://github.com/django/django/pull/6898>.
* Add support for indexes to inspectdb - This depends on
!6857 <https://github.com/django/django/pull/6857> so I
will send a PR once indexes are added to Meta class;
Current work on my local branch -
https://github.com/akki/django/commits/gsoc-indexes-inspectdb
<https://github.com/akki/django/commits/gsoc-indexes-inspectdb>
On Tuesday, 5 July 2016 11:54:00 UTC+5:30, akki wrote:
* Restructure index migrations
PR - https://github.com/django/django/pull/6866
<https://github.com/django/django/pull/6866>
Modified the internal working of migrations/schema
methods related to indexes. This mainly aims at
stabilising the newly added migrations for Indexclass.
* Introduce Meta.indexes
PR ready for review at
https://github.com/django/django/pull/6857
<https://github.com/django/django/pull/6857>.
Ticket - https://code.djangoproject.com/ticket/26808
<https://code.djangoproject.com/ticket/26808>
On Tuesday, 28 June 2016 18:44:37 UTC+5:30,
[email protected] wrote:
Wonderful! I make heavy use of btree_gin in one of my
projects; will be great to have these new Index classes!
On Monday, June 27, 2016 at 6:51:31 PM UTC-4, Tim
Graham wrote:
Support for more index types is planned. This is
only part 1 of the work. Please see
https://gist.github.com/akki/7fd50505928dac58dc350e6cb186a404
<https://gist.github.com/akki/7fd50505928dac58dc350e6cb186a404>
for the timeline.
On Monday, June 27, 2016 at 5:02:06 PM UTC-4,
[email protected] wrote:
Will it be possible to create indexes other
than btree? In reviewing the code it doesn't
look like it but I hope I'm wrong. It'd be
awesome to support the many more specific
index options without using run_sql.
--
You received this message because you are subscribed to the Google
Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
To post to this group, send email to
[email protected]
<mailto:[email protected]>.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/be05e9f0-ed44-4c73-aa41-b02349584e29%40googlegroups.com
<https://groups.google.com/d/msgid/django-developers/be05e9f0-ed44-4c73-aa41-b02349584e29%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
Jani Tiainen
--
You received this message because you are subscribed to the Google Groups "Django
developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/579746BE.9080803%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
