On Wed, 2007-06-20 at 14:43 -0300, Joao Morais wrote: > Joost van der Sluis wrote: > > > Those are the basics. If you have questions, ask them here. > > I have two! > > - please send me some hints to configure a query as fast as possible -- > read only and unidirectional. I will open the query, read everything and > close it.
Set ParseSQL to false. (This wil automatically set readonly to true) It won't be unidirectional, but I made an unidirectional TSQLQuery once, and coudn't measure any speed difference. The difference was to small. And maybe you could tweak packetrecords. Set it to -1 so that all data is fetched at once. That's faster if you really need all data immediately. (Consumes more memory, though) > - what about RowsAffected? You mean how many rows are affected by the last query you've run? I saw request for that earlier. But imho, you never need it. You always should know how many rows are affected before you execute a query. It could be a debug-tool, though.Maybe I could implement it. Maybe for one specific connection, or maybe even in a general form. Joost. _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
