[Oledb-dev] Update support

[Konstantin Izmailov]

Shachar,
I think you're right. As far as I remember ADO always opens a rowset as
read-only in client side cursor mode.

Regards
Konstantin


On 4/21/06, Shachar Shemesh <psql at shemesh.biz> wrote:
>
> Hi Victor,
>
>
> First, you have not submitted your one-liner for update support, which
> is the reason we did not have this discussion yet. No need to submit it
> now.
>
>
> I do believe that the solution you propose is not the right solution to
> the problem, but I'm looking for more input. What your proposed solution
> does, if I understand it correctly, is to tell the client that the
> columns we return are updateable.
>
>
> For the moment I will skip questions such as "should a column containing
> the table's primary key be marked "updateable", and would like, instead,
> to focus on the main thing - the update are never flushed back to the
> back end. The way I understand this patch, the client performs updates,
> believing that these updates will be saved in the database. This is
> something that never actually happens. I simply cannot sign off on a
> patch that causes the driver to lie to the client in such a blatant way.
>
>
> Am I missing something here?
>
>
>          Shachar
> _______________________________________________
> Oledb-devel mailing list
> Oledb-devel at pgfoundry.org
> http://pgfoundry.org/mailman/listinfo/oledb-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://pgfoundry.org/pipermail/oledb-devel/attachments/20060421/f6b4a8a7/attachment-0001.html