Hello Helen,

AutoCommit = False to use the rollback setup. I don'r think
that it affects the internal generated SQL which is reflected
in IB_WISQL. I traced the code and it seems to end up in
an API-call named something like xxx.UpdateRow.

I really want to know ,if every field change triggers a re-write
of the entire row including all blob info. If so , to optimize
for speed, I have to redesign my database to replace blobs by a
short field indicating where the real blob is located.

Best Regards,
Hans
======================================

Helen Borrie wrote:

>
> At 07:34 PM 18-08-01 -0600, you wrote:
> >Hello Jason,
> >
> >Using 4.2Ea
> >
> >Created same table
> >
> >CREATE TABLE TEST (
> > A INTEGER NOT NULL
> >, b INTEGER
> >, c INTEGER
> >, d INTEGER
> >,
> > PRIMARY KEY ( A )
> >)
> >
> >Created a TIBOTable, TIBOQuery and TIB_Query
> >
> >for each of the IB Objects
> >
> >1. Emptied table TEST
> >2. Appended a record
> >3. TESTA.Value := 1; or equivalent method for the object
> >4. TEST.POST
> >
> >5. TEST.Edit
> >6 TESTA.Value := 2;
> >7. TEST.Post;
> >
> >All some on step 6 or simular
> >
> >EXECUTE STATEMENT
> >TR_HANDLE = 32876440
> >STMT_HANDLE = 32871040
> >PARAMS = [ Version 1 SQLd 5 SQLn 5
> > TEST.A = 2
> > TEST.B = <NULL>
> > TEST.C = <NULL>
> > TEST.D = <NULL>
> > TEST.A[OLD_A] = 1 ]
> >
> >Does this mean a single field update, results in an update of the
> >entire Row? For some reason I thought TIB_Query only issued
> >an update for Field A in prior versions.
> >
> >How can I force the internal generation of a SQL update for
> >the changed/updated fields only ?
>
> Hans,
> Did you have autocommit on or off? These look like the params for the INSERT.
>
> Helen
>
> All for Open and Open for All
> InterBase Developer Initiative · http://www.interbase2000.org
> _______________________________________________________
>
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/