| Subject | Re: [IBO] Can't connect over the internet with TDataset query. |
|---|---|
| Author | Helen Borrie |
| Post date | 2006-10-01T14:14:09Z |
At 09:12 PM 1/10/2006, you wrote:
Open only opens the cursor and doesn't fetch any rows. Rows are then
requested one-by-one by calling First and (subsequently) Next.
With TIBOQuery on a slow connection, you're probably seeing a Very
Long Wait for the first batch of rows to arrive and more long waits
as the cursor buffers in your application swap rows in and out. If
you have blobs in the multi-row output, it will be worse. Modify the
query so that you fetch only a small amount of data and you'll see
something a lot sooner. But avoid scrolling interfaces on an
internet connection: they demand too much network traffic to be
practicable in that environment.
Helen
>I successfully connect to Firebird (V1.53) on a server using aTIB_Cursor and TIBOQuery have different behaviour. TIB_Cursor at
>TIBODatabase component via VPN over the internet.
>
>I can then successfully prepare and open a TIB_Cursor.
>
>But if I try the same with TIBOQuery, with an identical query to the
>TIB_Cursor, it freezes with a permanent hourglass.
>
>The same behaviour occurs both at runtime and design time, and I have
>tested on more than one server, so I suspect a problem with the
>TIBOQuery component.
>
>Any illumination or suggestions?
Open only opens the cursor and doesn't fetch any rows. Rows are then
requested one-by-one by calling First and (subsequently) Next.
With TIBOQuery on a slow connection, you're probably seeing a Very
Long Wait for the first batch of rows to arrive and more long waits
as the cursor buffers in your application swap rows in and out. If
you have blobs in the multi-row output, it will be worse. Modify the
query so that you fetch only a small amount of data and you'll see
something a lot sooner. But avoid scrolling interfaces on an
internet connection: they demand too much network traffic to be
practicable in that environment.
Helen