HI, Karol

Thanks for the suggestion. I'm using DISCHARGE_DATE + 0 instead. What I
don't understand is why its keep changing in different versions. Its a
nightmare for us to maintain the databases. I have received a numerous if
calls from my customers (We have thousands customers that using Firebird)
that complaints the speed issues after upgrading to v2.1.4.

Regards,

William


On Fri, Apr 1, 2011 at 1:30 AM, karolbieniaszewski <
liviuslivius@...> wrote:

>
>
>
> --- In firebird-support@yahoogroups.com, Wei Yu <william.wei.yu@...>
> wrote:
> >
> > OK. I changed the stored procedure a bit so now I can see the plans. the
> > only different:
> >
> > under 2.1.3, Indexes used for INCIDENT: only IDX_INCIDENT_CLIENTID
> >
> > under 2.1.4, Indexes used for INCIDENT: IDX_INCIDENT_CLIENTID and
> > IDX_INCIDENT_DISCHARGEDATE.
> >
> >
> > William
> >
> >
> > > What is plan produced in 2.1.3 and 2.1.4
> > > if you can not get detailed plan when do
> > > select * from schedule_getclientlist('19', -1, 'Y', 'N');
> > >
> > > then try change this proc to execute block and get detailed plan
> > > and we will see where is different
> > >
> > > Karol Bieniaszewski
> > >
> > >
> > >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
> I suppose that is because of this
> "DISCHARGE_DATE is null" and you have many null there?
>
> change this to COALESCE(DISCHARGE_DATE, '')=''
>
> Karol Bieniaszewski
>
>
>

[Non-text portions of this message have been removed]