Received: by 10.236.73.195 with SMTP id v43mr1187348yhd.70.1306468257424;
        Thu, 26 May 2011 20:50:57 -0700 (PDT)
X-BeenThere: django-haystack@googlegroups.com
Received: by 10.151.136.10 with SMTP id o10ls1703883ybn.3.gmail; Thu, 26 May
 2011 20:50:56 -0700 (PDT)
Received: by 10.236.180.201 with SMTP id j49mr1085124yhm.46.1306468256713;
        Thu, 26 May 2011 20:50:56 -0700 (PDT)
Received: by 10.236.180.201 with SMTP id j49mr1085123yhm.46.1306468256699;
        Thu, 26 May 2011 20:50:56 -0700 (PDT)
Return-Path: <polarc...@gmail.com>
Received: from mail-gx0-f175.google.com (mail-gx0-f175.google.com [209.85.161.175])
        by gmr-mx.google.com with ESMTPS id s34si116395yhh.5.2011.05.26.20.50.56
        (version=TLSv1/SSLv3 cipher=OTHER);
        Thu, 26 May 2011 20:50:56 -0700 (PDT)
Received-SPF: pass (google.com: domain of polarc...@gmail.com designates 209.85.161.175 as permitted sender) client-ip=209.85.161.175;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of polarc...@gmail.com designates 209.85.161.175 as permitted sender) smtp.mail=polarc...@gmail.com; dkim=pass (test mode) header...@gmail.com
Received: by gxk3 with SMTP id 3so621395gxk.20
        for <django-haystack@googlegroups.com>; Thu, 26 May 2011 20:50:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:in-reply-to:references:date
         :message-id:subject:from:to:content-type:content-transfer-encoding;
        bh=0WDJDWrTCt9H6t4s5duRaRivMULKwV4+rdwYRVeWHCw=;
        b=Df3NyRXoTTTIZV9dw7yd0oQFLQMdumPDPiEl7ADRPc8RFGLAuEwPrgBGRAsmJ24FL9
         LyKPDbVA8LWtbsT/lHOPIvBSNIrq1dRxnqMORfGI0jWC5euX8lRQs0k3bpQUOyNk0iwV
         QH+eqLNVuSLw2CV1RFcekweAOH0PosVDJhOAo=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=n8LqYHfkCwlJZeocPJXwo0SSJEKON1hypoFLGOVYKNKSIiTcLeBGsFOJ0t33VcCVJb
         0nqwZMVkL45Q5YrN1+p3K4l5RoVS5cgrR90dbb1TZf+6bHLpXx+jadbomTIzih1Ab54H
         6pDweJdkR3Ej3JzeqWMLV+zh4LKkiqaME8+pY=
MIME-Version: 1.0
Received: by 10.100.81.6 with SMTP id e6mr1146298anb.90.1306468256495; Thu, 26
 May 2011 20:50:56 -0700 (PDT)
Received: by 10.101.126.11 with HTTP; Thu, 26 May 2011 20:50:56 -0700 (PDT)
In-Reply-To: <2a69463f-652b-4cb7-8617-503691b4f...@22g2000prx.googlegroups.com>
References: <d58e2118-2968-4d3e-979a-9a424a48e...@w10g2000yqa.googlegroups.com>
	<1c0b10b6-83d3-48f7-99d2-4ae9c61a2...@p19g2000yqh.googlegroups.com>
	<BANLkTikBJOZ1wwLib_PLAu86za7FvAG...@mail.gmail.com>
	<2a69463f-652b-4cb7-8617-503691b4f...@22g2000prx.googlegroups.com>
Date: Thu, 26 May 2011 22:50:56 -0500
Message-ID: <BANLkTinezwb7FKbtaNsVqXe0JLEYwFQ...@mail.gmail.com>
Subject: Re: [django-haystack] Re: Haystack 1.2 released
From: Daniel Lindsley <polarc...@gmail.com>
To: django-haystack@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Craig,


   Ah, that is a problem. I'm out of time tonight. Can you please file
an issue on it & I'll get a fix out tomorrow night? Thanks,


Daniel



On Thu, May 26, 2011 at 12:32 AM, Craig de Stigter
<craig.destig...@onetrackmind.co.nz> wrote:
> Hi
>
> I've found one incompatibility with 1.1. SearchIndex.get_queryset()
> has been renamed to index_queryset().
>
> If you've overridden get_queryset() on a custom index, you'll need to
> rename your overridden method to index_queryset() also, otherwise it
> won't get called by the management commands.
>
> Craig
>
> On May 6, 3:09=A0pm, Daniel Lindsley <polarc...@gmail.com> wrote:
>> hellboy,
>>
>> =A0 =A0As far as I know, there are no backward-incompatibilities between
>> 1.1 & 1.2. No one has reported anything that I've seen & I take care
>> to try to not break things.
>>
>> =A0 =A0There will be backward-incompatible changes between 1.2 & 2.0. I'=
m
>> using it as a chance to clean up some pain points & make things
>> better. There will be a documented migration path for moving from 1.2
>> to 2.0 once I get closer to release time.
>>
>> Daniel
>>
>>
>>
>>
>>
>>
>>
>> On Thu, May 5, 2011 at 3:30 AM, hellboy <pbon...@googlemail.com> wrote:
>> > Is there gibts backwards incompatible changes between 1.1 and 1.2?
>>
>> > Between 1.2.x and 2.0?
>>
>> > Thank you.
>>
>> > --
>> > You received this message because you are subscribed to the Google Gro=
ups "django-haystack" group.
>> > To post to this group, send email to django-haystack@googlegroups.com.
>> > To unsubscribe from this group, send email to django-haystack+unsubscr=
ibe@googlegroups.com.
>> > For more options, visit this group athttp://groups.google.com/group/dj=
ango-haystack?hl=3Den.
>
> --
> You received this message because you are subscribed to the Google Groups=
 "django-haystack" group.
> To post to this group, send email to django-haystack@googlegroups.com.
> To unsubscribe from this group, send email to django-haystack+unsubscribe=
@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/djan=
go-haystack?hl=3Den.
>
>