Subject | Re: [IBO] Is IBX better than IBO when used threaded ? |
---|---|
Author | Lucas Franzen |
Post date | 2003-11-05T15:36:05Z |
Pelle,
Pelle F. S. Liljendal schrieb:
This will speed up your inserts at least by factor 10!
I do keep to the rule:
(a) IB_Query (or IBOQuery in your case) is for:
Selecting data that are shown to the user, eg browsing (but please don't
do a SELECT *, just select the fields you think you have to show within
a grid. If you use SELECT * be sure you have only a few records (best:
one) to show).
(b) TIB_Cursor: processing data that have to be selected from the server
but not be shown to the user
(c) TIB_DSQL: Doing INSERT, UPDATE, DELETE statements, even used for
executing non selectable stored procs
Following these rules you'll get a real fast application.
My 2 c.
Luc.
Pelle F. S. Liljendal schrieb:
> No doubt the fact that TIB_Cursor is unbuffered (compared toVery good.
> TIBOQuery that is not), is one of the major reasons I see a hugh
> speed gain. Also I am doing things a bit different now: E.g. several
> places when I needed to insert new data I would use a TIBOQuery
> where I would set SQL.TEXT to somthing like "select f1, f2, f3 from
> table where f1 = :f1" (then "Open", do a lot
> of "Insert"/"Post", "Close"). I now use a IB_DSQL where I simply set
> SQL.TEXT to something like "insert into table (F1,F2,F3) values
> (:F1, :F2, :F3)".
This will speed up your inserts at least by factor 10!
I do keep to the rule:
(a) IB_Query (or IBOQuery in your case) is for:
Selecting data that are shown to the user, eg browsing (but please don't
do a SELECT *, just select the fields you think you have to show within
a grid. If you use SELECT * be sure you have only a few records (best:
one) to show).
(b) TIB_Cursor: processing data that have to be selected from the server
but not be shown to the user
(c) TIB_DSQL: Doing INSERT, UPDATE, DELETE statements, even used for
executing non selectable stored procs
Following these rules you'll get a real fast application.
My 2 c.
Luc.