[Oledb-dev] Update support

[Konstantin Izmailov]

Victor,
sorry I kinda misled you. Actually it is the Provider responsibility to set
column flags via
  col->dwFlags |= DBCOLUMNFLAGS_WRITE + DBCOLUMNFLAGS_WRITEUNKNOWN
when lock type is not read-only. Do you know what to check to determine type
of lock used by ADO?

I do not remember any particular article or doc that described this. I used
ADO source code when worked on similar project long time ago. Unfortunately,
the source is MS proprietary and not available.

Anyway you figured it out. ADO's client cursor engine (CCE) copies whole
rowset into memory. Provider does not own that rowset. When a change occurs
ADO issues an UPDATE and modifies the corresponding row in memory. I think
as long as PgOledb sets column flags correctly, it would not be necessary to
implement neither IRowsetChange nor IRowsetUpdate.

Regards
Konstantin

On 4/21/06, Victor Snezhko <snezhko at indorsoft.ru> wrote:
>
> "Konstantin Izmailov" <kizmailov at gmail.com> writes:
>
> > Shachar,
> > I think you're right. As far as I remember ADO always opens a rowset
> > as read-only in client side cursor mode.
>
> Hi, Konstantin,
>
> Could you please point me to the specs (or examples, or articles)
> that confirm this?
>
> BTW, when I specify ADO recordset lock type as read-only, updating
> doesn't work even with my flag set.
>
> --
> WBR, Victor V. Snezhko
> E-mail: snezhko at indorsoft.ru
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://pgfoundry.org/pipermail/oledb-devel/attachments/20060422/23db51f9/attachment.html