- Introduce Meta.indexes - !6857 <https://github.com/django/django/pull/6857>, #26808 <https://code.djangoproject.com/ticket/26808> The PR <https://github.com/django/django/pull/6857> has been merged. Now class based indexes can be added using Meta.indexes <https://docs.djangoproject.com/en/dev/ref/models/options/#django.db.models.Options.indexes> . - Add support for column ordering (ASC/DESC) in class based indexes - !6982 <https://github.com/django/django/pull/6982>, #20888 <https://code.djangoproject.com/ticket/20888/> Resolve test failures on Oracle Update according to review suggestions - Resolve bug when unique_together was dropped along with it's field - #26180 <https://code.djangoproject.com/ticket/26180> Solve with another approach by introducing *[Add|Remove]UniqueTogether* operations and removing *generate_altered_unique_together* method of *migrations.Autodetector* PR - https://github.com/django/django/pull/7038 - Add support for GIN indexes Add *BtreeGinExtension* operation to *contrib.postgres* to create btree_gin extension Add *GinIndex* to *contrib.postgres.indexes* Ticket - https://code.djangoproject.com/ticket/27030 PR - https://github.com/django/django/pull/7046
On Tuesday, 2 August 2016 11:12:27 UTC+5:30, akki wrote: > > > > - Add support for column ordering (ASC/DESC) in class based indexes > Completed - tests, docs, code > PR - https://github.com/django/django/pull/6982 > > - Implement Hash index class > Add capability to get type of index in introspection (required for > testing this feature) > Completed - Add tests, docs, code > PR - https://github.com/django/django/pull/6995 > Ticket - https://code.djangoproject.com/ticket/26974 > > - Some minor changes in !6857 > <https://github.com/django/django/pull/6857> > > Other than these, I also had a look at btree_gin indexes and extensions > but haven't started the implementation yet. > > On Wednesday, 27 July 2016 20:26:38 UTC+5:30, akki wrote: >> >> Hi Jani >> >> Thanks a lot for offering help. I did face some issues with the Oracle >> setup in the beginning but was able to resolve them yesterday. :) >> You are most welcomed to review the PR and offer any suggestions for >> improvement at https://github.com/django/django/pull/6982/. The work >> related to the feature is in progress but the introspection-related work is >> mostly complete. >> >> Regards >> Akshesh(akki) >> >> On Tuesday, 26 July 2016 16:47:32 UTC+5:30, Jani Tiainen wrote: >>> >>> 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. >>>> Ticket - 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. >>>> 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 >>>>>> Modified the internal working of migrations/schema methods >>>>>> related to indexes. This mainly aims at stabilising the newly added >>>>>> migrations for Index class. >>>>>> >>>>>> >>>>>> - Introduce Meta.indexes >>>>>> PR ready for review at https://github.com/django/django/pull/6857. >>>>>> Ticket - https://code.djangoproject.com/ticket/26808 >>>>>> >>>>>> >>>>>> On Tuesday, 28 June 2016 18:44:37 UTC+5:30, thinkwel...@gmail.com >>>>>> 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 for >>>>>>>> the timeline. >>>>>>>> >>>>>>>> On Monday, June 27, 2016 at 5:02:06 PM UTC-4, thinkwel...@gmail.com >>>>>>>> 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 django-develop...@googlegroups.com. >>> To post to this group, send email to django-d...@googlegroups.com. >>> 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?utm_medium=email&utm_source=footer> >>> https://groups.google.com/d/msgid/django-developers/be05e9f0-ed44-4c73-aa41-b02349584e29%40googlegroups.com >>> . >>> 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. 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/9c8007ab-8f8a-4475-803a-0bde8d689ce7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
