Subject | Re: [IBO] More on problem with SearchingLinks. See Message 17027 |
---|---|
Author | Helen Borrie |
Post date | 2002-11-07T11:02:45Z |
At 09:26 AM 07-11-02 +0000, you wrote:
on a column that might contain nulls. I see no point in searching for
something that will never be found. If I knew I was going to use a column
for searching, I'd make sure that every row had at least a default value
there.
disorderly heap at the bottom of the dataset and that is where the
searching cursor ends up...nothing found, nowhere to go. I suggest that
you add a where subclause to your query, ..'and MySearchingColumn is not
null'... so that you don't even get those null records in the set...or
reconsider the usefulness of setting a searchinglink on a column that has
so many nulls.
Helen
>Hi forum.No.
>
>I have the same problem as it appears on Message 17027 (please see it)
>about the SearchingLinks. I have read that messages, and I have discover
>that the problem happens when the column on which you do the ordering
>(searching) is not defined as "NOT NULL" on Interbase.
>
>To Team IBO: Is this a bug in IBO
>or is it the desired effect?I wouldn't desire such an effect. But then I wouldn't put searchinglinks
on a column that might contain nulls. I see no point in searching for
something that will never be found. If I knew I was going to use a column
for searching, I'd make sure that every row had at least a default value
there.
>The biggest problem is that all data in a TIB_Grid disappears.It disappears out of sight. All of your records with nulls are in a big
disorderly heap at the bottom of the dataset and that is where the
searching cursor ends up...nothing found, nowhere to go. I suggest that
you add a where subclause to your query, ..'and MySearchingColumn is not
null'... so that you don't even get those null records in the set...or
reconsider the usefulness of setting a searchinglink on a column that has
so many nulls.
Helen