Jason,

I think upWhereChanged better than upWhereAll, because this uses only key field and fields
that have changed are used to find the record.

Thus if another user changed the same record but it did not change the field that is being changed by the current user, the update would be successful.

And regarding property IB_TransUpdate, what do you think?

Regards


PHA
Nova Odessa / SP - Brazil

----- Original Message -----
From: "Jason Wharton" <jwharton@...>
To: <IBObjects@yahoogroups.com>
Sent: Wednesday, January 30, 2002 8:52 PM
Subject: Re: [IBO] New options for IBO.


> For now I support two of those. The middle one doesn't make sense to me. Can
> someone convince me otherwise?
>
> If you want upWhereAll behavior, flip CachedUpdates to true (this includes
> when using MIDAS) and for normal stuff upWhereKeyOnly is sufficient.
>
> If you want something more fancy, then you have to control it yourself.
>
> Regards,
> Jason Wharton
> CPS - Mesa AZ
> http://www.ibobjects.com
>
>
> ----- Original Message -----
> From: "Paulo Henrique Albanez" <pha@...>
> To: <IBObjects@yahoogroups.com>
> Sent: Wednesday, January 30, 2002 8:04 AM
> Subject: [IBO] New options for IBO.
>
>
> > Jason, I would like to know if is possible includes these property in IBO.
> >
> > type TUpdateMode = (upWhereAll, upWhereChanged, upWhereKeyOnly);
> >
> > Value - Meaning
> > upWhereAll - All columns (fields) are used to locate the record.
> > upWhereChanged - Only key field values and the original value of fields
> that have changed are used to find the record.
> > upWhereKeyOnly - Only key fields are used to find the record.
> >
> > To have a larger control, when IBO generates EditSQL.
> >
> > It would like to use upWhereChanged mode, to avoid the use of the property
> PessimisticLocking, because this calls Before/After Updates Triggres.
> >
> >
> > IB_TransUpdate: TIB_Transaction
> >
> > When this was informed, it would be used in the internal component
> TIB_UpdateSQL, isolating the update transaction of the navigation
> transaction.
> >
> > This property together with CacheUpdates, it would solve several problems,
> like Refesh in the tables, when executes a CommitRetaining.
> >
> > TClientDataSet with DBExpress, they use this concept.
> > Regards
> >
> > PHA
> > Nova Odessa / SP - Brazil
>
>
>
>
> ___________________________________________________________________________
> IB Objects - direct, complete, custom connectivity to Firebird or InterBase
> without the need for BDE, ODBC or any other layer.
> ___________________________________________________________________________
> http://www.ibobjects.com - your IBO community resource for Tech Info papers,
> keyword-searchable FAQ, community code contributions and more !
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
>


[Non-text portions of this message have been removed]