Tim,

Not the answer I wanted -- I could fix it if it was my problem -- but, for
now, the impact is minimal, as I have already converted my searches to
canned queries.

A couple of quick questions. Firstly, it seems that, using ExecSQL, that if
the search yields no results then the query is never opened. Just want to
verify this.

Secondly, is there any rough ETA (say, month) for ElevateDB?

Jerry

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:6CEA7660-D958-4B62-AE05-689C53504CAE@news.elevatesoft.com...
| Jerry,
|
| << I think you may have to examine the project and database I sent you to
| see what is happening. >>
|
| I got your database and yes, never mind what I said about the filter index
| threshhold setting, it's not the ordering issue.  The issue is that the
BLOB
| values are very large in the table, and DBISAM has to re-evaluate the
| TextSearch() condition on the BLOB values as it does repositioning to
ensure
| that any changes to the table are reflected properly.  It's all rather
| complicated, but it has to do with the changes in 4.x several minor
releases
| ago where we reduced the time that read locks are held for brute-force
| filters and queries on a table.
|
| The only workaround at this point is to use a canned query result set,
which
| won't have this issue.  ElevateDB doesn't have this issue because we did
not
| repeat the same design that the later 4.x issues had with respect to the
| read locking, and I'm definitely considering putting DBISAM back the way
it
| was at some point also.
|
| --
| Tim Young
| Elevate Software
| www.elevatesoft.com
|
|

Jerry,

<< Not the answer I wanted -- I could fix it if it was my problem -- but,
for now, the impact is minimal, as I have already converted my searches to
canned queries. >>

Well, it's another unintended consequence from the read locking changes that
we made, and it's not something that I'm happy about either.

<< A couple of quick questions. Firstly, it seems that, using ExecSQL, that
if the search yields no results then the query is never opened. Just want to
verify this. >>

Yes, ExecSQL can tell when there is a result set to open, and then opens it
as necessary.

<< Secondly, is there any rough ETA (say, month) for ElevateDB? >>

We should have a preview available this week, and then it's just a matter of
getting the documentation and automated tests done.  I anticipate this to
take until the end of the month.

--
Tim Young
Elevate Software
www.elevatesoft.com

Great.

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:26F11FD6-996A-4978-81C0-8AC361ACB508@news.elevatesoft.com...
| << Secondly, is there any rough ETA (say, month) for ElevateDB? >>
|
| We should have a preview available this week, and then it's just a matter
of
| getting the documentation and automated tests done.  I anticipate this to
| take until the end of the month.