Subject | Re: [IBO] Updating updated fields only |
---|---|
Author | danielrail |
Post date | 2005-04-07T17:54:15Z |
--- In IBObjects@yahoogroups.com, "Jason Wharton" <jwharton@i...>
wrote:
the EditSQL(UPDATE statement) and set PreparedEdits to False, the
dataset is marked as not updatable, even if there's no aggregate
fields and only one table is in the query. And, if I put a statement
in EditSQL and set PreparedEdits to False, then the full UPDATE
statement as defined in EditSQL is used. I haven't checked with
TIB_Query to see if it handles this better, which I probably would
expect it to.
Daniel Rail
wrote:
> Kevin,fields are
>
> > Is there a way to tell IBO datasets (either native or
> > TDataset compatible)
> > to update only those fields that have changed. My current
> > issue is with the
> > TIB_Query.
> >
> > If I remember correctly, the TQuery had an UpdateMode which
> > lets us specify
> > upWhereAll, upWhereChanged, upWhereKeyOnly.
> >
> > I *really* hope IBO has this functionality.
>
> IBO does have some ways to influence things along these lines.
>
> There is a property PreparedEdits that determines if only changed
> included in the UPDATE SQL that is sent to the server or if aprepared
> UPDATE SQL is held for all fields and kept prepared and every timea change
> is posted all column values are submitted. By default it uses aprepared
> edit statement and submits all column values. Setting it to falseallows
> IBO to generate a unique SQL for each record posting including onlychanged
> columns.This doesn't work for me, and I'm also using TIBOQuery. If I omit
the EditSQL(UPDATE statement) and set PreparedEdits to False, the
dataset is marked as not updatable, even if there's no aggregate
fields and only one table is in the query. And, if I put a statement
in EditSQL and set PreparedEdits to False, then the full UPDATE
statement as defined in EditSQL is used. I haven't checked with
TIB_Query to see if it handles this better, which I probably would
expect it to.
Daniel Rail