Michael,

<< Thanks, so i must have 2 index fields for doing this fast right ? (One
Index and One Text Index for the same field) >>

No, just the text index.  It should be selective enough (usually) so that
the LIKE only has to visit a few rows during its evaluation.

--
Tim Young
Elevate Software
www.elevatesoft.com

Dear Tim,

> << Thanks, so i must have 2 index fields for doing this fast right ? (One
> Index and One Text Index for the same field) >>
>
> No, just the text index.  It should be selective enough (usually) so that
> the LIKE only has to visit a few rows during its evaluation.

Thanks Tim, i'll give it a try.

btw, if I add an additional Index (no text index) to the same field
shouldn't improve the performance ? (As i said i don't care about disk
space)

btw, will it produce a sensitive result ?

--
Charalampos Michael - [Creation Power] - http://www.creationpower.gr

Michael,

<< btw, if I add an additional Index (no text index) to the same field
shouldn't improve the performance ? (As i said i don't care about disk
space) >>

Probably not, because ElevateDB will most likely ignore the index and just
read the rows from disk anyway.  Remember, it uses fairly-accurate cost
estimates to determine the most efficient way to evaluate a particular
condition.

<< btw, will it produce a sensitive result ? >>

Sure, as long as RequestSensitive=True and you're not using an ORDER BY
clause that would force an insensitive result set.

--
Tim Young
Elevate Software
www.elevatesoft.com

Dear Tim,

> << btw, will it produce a sensitive result ? >>
>
> Sure, as long as RequestSensitive=True and you're not using an ORDER BY
> clause that would force an insensitive result set.

Unfortunately i use ORDER BY ... So no solution for this right ?

--
Charalampos Michael - [Creation Power] - http://www.creationpower.gr

Charalampos


As long as there's an index matching the ORDER BY clause you'll get a sensitive result set

Roy Lambert [Team Elevate]

Dear Roy,

> As long as there's an index matching the ORDER BY clause you'll get a sensitive result set

You're correct ... But it isn't possible to produce a sensitive result
with GROUP BY right ?

I guess GROUP BY can't produce sensitive result in any RDBS.
IOW, it's not possible and never be ... right ?

--
Charalampos Michael - [Creation Power] - http://www.creationpower.gr

Michael,

> I guess GROUP BY can't produce sensitive result in any RDBS.
> IOW, it's not possible and never be ... right ?

As Roy told you: if there is an index on the field you are grouping the
result can be sensitive.

Uli

Charalampos


Correct - unless you can tell me what would be sensitive

Roy Lambert

Dear Uli,

>> I guess GROUP BY can't produce sensitive result in any RDBS.
>> IOW, it's not possible and never be ... right ?
>
> As Roy told you: if there is an index on the field you are grouping the
> result can be sensitive.

Are you sure ? I just tried and the result was read-only.
(I have an index on the group field)

select * from employees
group by name

The result set was insensitive and read-only
The result set consisted of zero or more rows

--
Charalampos Michael - [Creation Power] - http://www.creationpower.gr

Dear Roy,

> unless you can tell me what would be sensitive

?

--
Charalampos Michael - [Creation Power] - http://www.creationpower.gr