On Delete - lock is not compatible with fetchAll=false

Discussion of open issues, suggestions and bugs regarding UniDAC (Universal Data Access Components) for Delphi, C++Builder, Lazarus (and FPC)
Post Reply
maddn
Posts: 13
Joined: Wed 21 Sep 2011 12:47

On Delete - lock is not compatible with fetchAll=false

Post by maddn » Wed 26 Oct 2011 14:27

When I want to delete a record of a Table with fetchall=false I get this Error-Message
lock is not compatible with fetchAll=false


Isn't it possible to delete Records on Tables without fetchingall?

AndreyZ

Post by AndreyZ » Thu 27 Oct 2011 10:20

You cannot delete records when FetchAll is False and LockMode is not lmNone. This is a specificity of working with not fetched data. To solve the problem set the LockMode property to lmNone. We will investigate this problem and ways to avoid it.

maddn
Posts: 13
Joined: Wed 21 Sep 2011 12:47

Post by maddn » Thu 27 Oct 2011 10:31

Hello AndreyZ first thank you for your answer. So we have a little Problem because we have very large Tables with Blobs which take a lot of time to open with fetchall=true. We also need lmPessimistic in all of our Table-Instances to have consistent data.

In fact, I wonder why it is possible to edit or insert but not to delete a record with fetchall=false and lmPessimistic.

Do you know when there'll be an update which fix that problem?

maddn
Posts: 13
Joined: Wed 21 Sep 2011 12:47

Post by maddn » Wed 02 Nov 2011 11:43

Hello again,

can you please tell me if there'll be an update which fix that problem?

AndreyZ

Post by AndreyZ » Wed 02 Nov 2011 13:39

We are investigating this problem. As soon as we have any results, we will let you know.

maddn
Posts: 13
Joined: Wed 21 Sep 2011 12:47

Post by maddn » Fri 04 Nov 2011 11:07

Hello AndreyZ, could you please give me more details when there'll be results. Does it last days, weeks or months? Deleting records with fetchall=false and lmPessimistic is very important for us and our decission for UniDAC.

AndreyZ

Post by AndreyZ » Tue 08 Nov 2011 10:02

We will solve this problem in the next UniDAC build. We plan to release UniDAC approximately in two weeks.

Post Reply