Subject | Re: R: [IBO] Is IBX better than IBO when used threaded ? |
---|---|
Author | Helen Borrie |
Post date | 2003-11-02T00:35:19Z |
At 01:18 PM 1/11/2003 +0000, you wrote:
Just to get back to the context of the test application - I'm not
suggesting that you shouldn't use persistent fields for your GUI. The VCL
GUI controls are designed to work that way, with the scrolling
dataset. The scrolling dataset works by targeting a single row and
selecting it for an operation, positioned updates and deletes.
The context of the test app was non-GUI. The point of my comment was -
don't use this component -- along with its positioned update features and
persistent fields and the additional overhead of the IBO wrapper -- for
searched operations that are invisible to the user.
Helen
>Hi Helen,Carlos,
>
> >>>TIBODataset has two column layers: one the VCL's persistent
> >>>fields and the other the TIB_Columns of the InternalDataset. The
> >>>trick is: Don't use persistent fields!
>
>I repeated the benchmarks and the results are almost the same, with
>or without persistent fields. Nevertheless persistent fields are
>useful when you don't want grids to auto create all the fields,
>instead being me who filter the ones I want to be seen, which for me
>is a must.
Just to get back to the context of the test application - I'm not
suggesting that you shouldn't use persistent fields for your GUI. The VCL
GUI controls are designed to work that way, with the scrolling
dataset. The scrolling dataset works by targeting a single row and
selecting it for an operation, positioned updates and deletes.
The context of the test app was non-GUI. The point of my comment was -
don't use this component -- along with its positioned update features and
persistent fields and the additional overhead of the IBO wrapper -- for
searched operations that are invisible to the user.
Helen