TUniTable or TUniQuery ?
Posted: Thu 11 Apr 2013 15:43
Does TUniTable work with the underlying table directly or does it just convert each operation into SQL statements such that I would be better off just using TUniQuery directly ?
I ask because often the examples given here show an SQL statement for the SELECT and then instead of using an Update will be shown a .Edit, fieldbyname = someval, .post operation. It makes me wonder if the table methods are a little faster than using SQL statements. But if TUniTable just calls TUniQuery under the covers then no reason to use it for that.
I ask because often the examples given here show an SQL statement for the SELECT and then instead of using an Update will be shown a .Edit, fieldbyname = someval, .post operation. It makes me wonder if the table methods are a little faster than using SQL statements. But if TUniTable just calls TUniQuery under the covers then no reason to use it for that.