Does TEDBQuery.OnProgress not work in C/S?

My query is

Select * from Contacts
Where LastName = 'Smith'

The query is on an unindexed column containing about 45,000 names, which
takes about 8 seconds to complete.  The OnProgress event only appears to
fire at the beginning (PercentDone = 0) and the end (PercentDone - 100).
 The session.ProgressTimeInterval is set to 1000 (the default).

Dale

Dale,

<< Does TEDBQuery.OnProgress not work in C/S? >>

No, it should be working just fine.

<< My query is

Select * from Contacts
Where LastName = 'Smith'

The query is on an unindexed column containing about 45,000 names, which
takes about 8 seconds to complete.  The OnProgress event only appears to
fire at the beginning (PercentDone = 0) and the end (PercentDone - 100).
The session.ProgressTimeInterval is set to 1000 (the default). >>

Are you requesting a sensitive result set ?  If so, then that is the reason.
Currently, the sensitive filtering does not indicate progress.   If you
request an insensitive result set, then you will see progress.

--
Tim Young
Elevate Software
www.elevatesoft.com

<<
Tim Young [Elevate Software] wrote:
Are you requesting a sensitive result set ?  If so, then that is the
reason.
Currently, the sensitive filtering does not indicate progress.   If you
request an insensitive result set, then you will see progress.
>>

Yes, it's a sensitive result set.  Is this something that can be added
to ElevateDB in the future?

Thanks,

Dale

Dale,

<< Yes, it's a sensitive result set.  Is this something that can be added to
ElevateDB in the future? >>

Yes, it's on the list.  It seems easy, but it is actually very difficult to
deal with.  EDB has to effectively "inventory" every operation that the
query intends to take, and then pass around this information so that each
operation knows how to update the progress accordingly.  A single query
could do a partial table scan, an index scan, a scan for deleted rows,
another index scan, etc.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim:

Any idea on when you can get to this feature?  Anyone else out there need it?

Dale

----------------------------------

"Tim Young [Elevate Software]" wrote:

Dale,

<< Yes, it's a sensitive result set.  Is this something that can be added to
ElevateDB in the future? >>

Yes, it's on the list.  It seems easy, but it is actually very difficult to
deal with.  EDB has to effectively "inventory" every operation that the
query intends to take, and then pass around this information so that each
operation knows how to update the progress accordingly.  A single query
could do a partial table scan, an index scan, a scan for deleted rows,
another index scan, etc.

--
Tim Young
Elevate Software
www.elevatesoft.com

Dale,

<< Any idea on when you can get to this feature?  Anyone else out there need
it? >>

I'll try moving it up on the list.  I might punt a little, and just segment
the progress and add separate status messages that indicate what is going
on.

--
Tim Young
Elevate Software
www.elevatesoft.com