On Mon, Feb 1, 2010 at 11:18 AM, Christophe Pettus wrote:
>
> On Jan 31, 2010, at 7:10 PM, Russell Keith-Magee wrote:
>>
>> However, as noted in [1], you don't need to post to django-dev just to
>> tell us you uploaded a patch.
>
> OK, sorry for the noise. Since I had uploaded the patch on 11/6/0
On Jan 31, 2010, at 7:10 PM, Russell Keith-Magee wrote:
However, as noted in [1], you don't need to post to django-dev just to
tell us you uploaded a patch.
OK, sorry for the noise. Since I had uploaded the patch on 11/6/09, I
wanted to make sure I hadn't missed a step in the review process
On Mon, Feb 1, 2010 at 11:05 AM, Christophe Pettus wrote:
> I've uploaded a patch for this ticket, which fixes a somewhat obscure
> problem:
Thanks for the patch.
However, as noted in [1], you don't need to post to django-dev just to
tell us you uploaded a patch. The core developers all track
dj
I've uploaded a patch for this ticket, which fixes a somewhat obscure
problem:
There is a bug in the handling of
InsertQuery.connection.features.can_return_id_from_insert, which is
causing Django 1.1.1 to throw a ProgrammingError exception when
inserting a new object/record into the datab
