Page 1 of 1

Move from Paradox to MariaDB, problem with Keys

Posted: Fri 16 Sep 2016 07:39
by Manfred.P
I moved a DB from Paradox to MariaDB. I use MyDac latest Version.
Each Record contains a Datefield and is sorted from latest to newest.
At Paradox I modified the Record and changed the Date to now. After that I go to the first Record.
With Paradox no Problem, but MyDac sends a select * from db at any changed row and this lasts very longer then on a Key.
There is no differenz if I set the Key-Field to IndesFieldNames or Orderfieldnames.
The Table contains a Index but I don't know how to use.

Manfred

Re: Move from Paradox to MariaDB, problem with Keys

Posted: Fri 16 Sep 2016 09:28
by ViktorV
In order to get a detailed answer, please compose a small sample demonstrating the described behavior and send it to viktorv*devart*com, including scripts for creating database objects.

Re: Move from Paradox to MariaDB, problem with Keys

Posted: Thu 22 Sep 2016 15:25
by Manfred.P
I solved the Problem. I set Limit from -1 to 20 and Fetchrows to 20.
TMyTable sends now
SELECT * FROM tb1 ORDER BY row1, row2 LIMIT 0, 20
The Server delivers only 20 instead of over 100000 Records.

Manfred

Re: Move from Paradox to MariaDB, problem with Keys

Posted: Thu 22 Sep 2016 15:40
by ViktorV
We are glad to see you have found a solution.
Feel free to contact us if you have any further questions about our products.