Contributing to ORM module

[evgen...@gmail.com]

Hi everyone!

First of all, I'm not sure that I'm writing in the right place, so excuse me if this so.

Second - let me introduce myself - my Name is Evgeniy, I'm active web developer (mostly Django) for at least one year, and I'm finishing university this winter by speciality "program engineering". So right now I'm choosing a theme for my diploma. My background in SQL databases is more deep, so I thought that I could implement some feature in Django's ORM module, and describe it in my graduation work.

The question is - is there available unimplemented features that should improve performance of ORM module and at the same time is not easy, but also is not incredible hard for one person like me? Thanks in advance, hope for answer!

[ludovic coues]

There is a list of bug and feature request on the django's tracker

https://code.djangoproject.com/query

> --
> 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/56d7e6ff-5ef4-45b7-bffe-631e773cd063%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



--

Cordialement, Coues Ludovic
+336 148 743 42

[Tim Graham]

You can filter tickets by "Component". You'll want to look at the "Database layer (models, ORM)" component.

There are plenty of non-trivial issues to tackle, although it requires a lot of time just to understand the basics. I'd recommend trying to tackle some small issues first. That'll give you a better understanding of how much work some of the larger issues might be.