Hi,
Thanks a lot for the hints and suggestions .I shall soon come back with a
detailed groundwork on the various areas that django could make use of its
own feature set.
On 10 March 2012 14:04, Russell Keith-Magee wrote:
>
> On 10/03/2012, at 3:48 PM, Karthik Abinav wrote:
>
> > Hi,
> >
> > I
I may have found a bug in Django but wanted to run it by the core
developers before I filed a ticket. It concerns validation of a
ModelMultipleChoiceField when using a case-insensitive database
collation (in our case, a MySQL database with collation set to
'utf8_general_ci').
First some background
On 10/03/2012, at 1:52 AM, Joe & Anne Tennies wrote:
> While, I generally agree with the current approach, especially this close to
> release. I'm going to play devil's advocate for a bit.
>
> Schema migrations have been talked about for quite a while. There are at
> least 3 external implement
On 10/03/2012, at 3:48 PM, Karthik Abinav wrote:
> Hi,
>
> I was looking through the google summer of code 2012 wiki page and found
> the "Best practices updates" problem interesting and would like to work
> towards it. It would be really nice, if someone could explain in more detail
> as t
On 10/03/2012, at 1:13 PM, h3 wrote:
> And this idea is just: a patch server.
>
> Imagine a site where developers can browse, upload, rate and comment
> patches. Something like django snippets, but instead of snippets, it's
> patches for django.
>
> A developer can upload a patch (linked or not
