> -----Original Message-----
> From: Nico Callewaert [mailto:nico.callewaert@...]
> Sent: Miércoles 14 de Marzo de 2001 14:29
>
> I'm concerned about one thing. To retrieve data from a
> table, I always
> use IB_Query, take care of the fact to only retrieve the rows of interest,
> and I always check the plan, so I'm sure, the statement is using the right
> index. I have a table now with 35.000 rows, it's still going fast, but
> what if the table will grow to 100.000 - 200.000 - 300.000 rows,
> ...., does
> it mean that the execution of the statements will always slow
> down, the more
> rows in the table ? Do I have to tell the users of my application, that
> the longer they will use the application the slower it will get,
> because the
> database will grow ?

I doubt a normal user is able to read 350.000 rows in a grid. Probably you
will have a WHERE clause to filter. The difference would be between
RequestLive being True or False. With True, it maps to the FOR UPDATE clause
and then IB sends one record at a time. Without it, IB will try to put more
than one record in a packet. This was an unfortunate decision that probably
has to be reverted in the future. A "live" request doesn't have to cause
this performance hit.

C.