44 results found
-
Add a limit for the record count in the DataSet
Add a parameter, for example, MaxFetchRows, which will limit the number of records which can be fetched to the DataSet.
83 votes -
Possibility to set options not just for each DataSet, but for the whole session
Currently such options as FetchAll, QueryRecCount, and others can be set for each DataSet separately. If you need to change these settings, you need either to do it manually at design-time or set them in cycle for all DataSets at run-time.
We may add an option to set these values for all DataSets for a connection. For example, if FetchAll is set to True for a connection, all DataSets in this connection will use this value. You need to set this property only for those DataSets, that must have different value of this option.
14 votes -
Forced sending queries to the server without parameters
Queries may be with or without parameters:
select *
from test_table
where id = :IDor
select *
from test_tableHowever some database servers execute queries without parameters faster than the same queries with parameters. An option (for example, AllowParams) may be added; if this option is set to False, all queries will be sent to a server as text.
45 votes -
Save settings to the database as in an *.ini file or in registry
Many applications use TiniFile or TRegistry for saving their settings. However sometimes one user can work on several workstations with his login and password. He wants to have the same settings on all of his workplaces, and that settings, saved on one computer, were available on other ones.
To implement this feature we may add classes or components with interface similar to TiniFile or TRegistry that save data not on the local computer, but in a database.
82 votes
- Don't see your idea?