Page 1 of 1
Problem with TClientDataset after upgrade to 7.2 from 7.1
Posted: Wed 14 Feb 2018 17:11
by zvasku
Hi all,
we have huge problem after upgrade Unidac to 7.2. We use TClientDataset-TDatasetProvide-TUniQuery to post data. Starting from version 7.2 one extra sql call is made before apply updates. It completely slow down applyupdates at all.
Example:
CDS.CommandText:='select * from TABLE where ID=10';
CDS.Open;
CDS.Insert;
...
CDS.Post;
CDS.ApplyUpdates(0); -- HERE TWO SQL EXECUTE
One sql is exact as in CommandText and the second is right INSERT INTO ....
Have I missed something in Options?
Thanks
Zdenek
Re: Problem with TClientDataset after upgrade to 7.2 from 7.1
Posted: Thu 15 Feb 2018 14:56
by azyk
Thank you for the information. We reproduced the specified difference in behavior and are investigating it now. We will let you know about the results.
Re: Problem with TClientDataset after upgrade to 7.2 from 7.1
Posted: Thu 15 Feb 2018 18:22
by zvasku
Perfect. Thanks
Zdenek
Re: Problem with TClientDataset after upgrade to 7.2 from 7.1
Posted: Tue 27 Feb 2018 14:32
by azyk
We fixed the issue. This fix will be included in the UniDAC next build.
If you want to get it before the official release, use the contact form at our site:
https://www.devart.com/company/contactform.html and provide us with UniDAC license number, as well as the email address where the night build can be sent to.
Re: Problem with TClientDataset after upgrade to 7.2 from 7.1
Posted: Sat 03 Mar 2018 18:14
by zvasku
Thanks. I can wait for official release.
Zdenek
Re: Problem with TClientDataset after upgrade to 7.2 from 7.1
Posted: Mon 12 Mar 2018 14:29
by gss200610
I have a similar problem:
clientdataset -> qdetail (tdatasetfield)
qmaster.sql.text: = SELECT * FROM MASTER
cdsmaster (clientdataset) -> provider -> qmaster:
here I use the dbedits connected to the clientdataset, if I am in the registry number 1 okay, more if I do:
qmaster.close;
qmaster.sql.text: = 'SELECT * FROM MASTER WHERE ID = 2';
qmaster.open;
cdsmaster.refresh -> I use to try to update the dbedits on the screen, therefore I did not find another way to position the clientdataset -> clientdataset error: Record not found or changed by another user
how to proceed, do you have some example of using clientdataset with uniquery and selecting a specific record in the query?
Re: Problem with TClientDataset after upgrade to 7.2 from 7.1
Posted: Wed 14 Mar 2018 10:31
by ViktorV
In order for us to be able to give you a detailed answer, we need to have a sample demonstrating the specified behavior. Therefore, please compose a small sample demonstrating the described behavior and send it to us using the contact form
https://devart.com/company/contactform.html, including the scripts for creating database objects.
Re: Problem with TClientDataset after upgrade to 7.2 from 7.1
Posted: Wed 15 Aug 2018 12:50
by zvasku
We try to move from 7.1 to 7.3 but still have problems with extra select. We have to stuck in 7.1, It's not good situation.
Re: Problem with TClientDataset after upgrade to 7.2 from 7.1
Posted: Tue 21 Aug 2018 09:30
by azyk
We cannot reproduce this issue on the latest version of UniDAC 7.3.9. Please send us a test project to reproduce it using the contact form at our site:
https://devart.com/company/contactform.html . In the sample, also include the script for creating a test table.
Re: Problem with TClientDataset after upgrade to 7.2 from 7.1
Posted: Tue 21 Aug 2018 13:19
by zvasku
Problem is with UpdateMode - keyOnly, I think. I will send an example code.
Re: Problem with TClientDataset after upgrade to 7.2 from 7.1
Posted: Thu 23 Aug 2018 10:07
by azyk
Thank for the sent sample. We reproduced the issue and are investigating it now. We will inform you about the results.