Sorry, but if you haven't started a proposal yet and haven't contributed to
Django before, it's unlikely you'll develop a successful proposal in less
than a week (the application deadline is Friday).
On Monday, March 21, 2016 at 2:59:43 PM UTC-4, aleksand...@gmail.com wrote:
>
> Hello, Tim.
>
>
Hello, Tim.
Is there free tasks for me, I'm a new one in django(0.5 year), but it's
really interesting for me and I want to be useful for us and have a good
summer with great experience.
waiting your answer and making a contribution, Alex
--
You received this message because you are subscribe
No, I'm not aware of any ongoing work or plans to add SQLAlchemy support.
Let's continue the discussion in a separate thread since this is now off
topic.
On Thursday, March 3, 2016 at 11:36:16 AM UTC-5, Asif Saifuddin wrote:
>
> Hi Tim,
>
> Thanks for your early input on the issue. I don't think
Hi Tim,
Thanks for your early input on the issue. I don't think I should compete
with any specific proposal which already have another better competitor. I
did some research on SQLalchemy backend support on django and relevant
improvement long ago before class based index. I will go for a sqla
FYI, I'm aware of another student working on a proposal for that project.
You're welcome to develop a competing proposal, but you're at a
disadvantage at this point since the other student has a track record of
successful contributions.
On Wednesday, March 2, 2016 at 2:46:29 PM UTC-5, Asif Saif
Hi Josh,
I'm willing to work on django orm improvment for gsoc and considering
custom index as a project idea. I have gone through the available resources
like dep, POC on class based index, unification of transform API etc. What
others stuff do you suggest me to look into to have some concrete
I added "Custom indexes" to the ideas list at
https://code.djangoproject.com/wiki/SummerOfCode2016. Feel free to revise
the description or add yourself as a possible mentor.
On Sunday, February 7, 2016 at 6:26:38 AM UTC-5, Josh Smeaton wrote:
>
> There are many places that expressions can extend
There are many places that expressions can extend to, and I think indexes
would make a really good candidate. There are a few things that need to
happen to make this work though.
- create meta.indexes to store { index_name: IndexType('field') }
- internally translate any db_index=True to the app
So, in #django recently there was a discussion about adding an index on
a date field for just the year.
I know the idea was raised some time ago, and several ideas on the
syntax were expressed. But most of that focused on different types of
indices - not on indexing expressions.
It occurr
