75 results found
-
Adding comment feature as property to UniDAC components
Add a "comment" property to possible UniDAC components. It could be very helpfull to add comments to TUniConnection, TUniQuery, TUniTable, ... because technical names are often short or meaningless and a comment can translate it into a meaningful description.
8 votes -
Add CSV import to virtual table in addition to existing XML import.
It would be good to have the ability to populate a table direct from CSV file
8 votes -
Please update the help file
Please update the help file, and try to be more explicit on the definitions
7 votes -
Improve the unified sql structure and macros
Extend the actual unified sql structure and macros to stored procedures, functions, views etc. to be able to create applications truly database independent.
more info at
http://www.devart.com/forums/viewtopic.php?t=15057&highlight=7 votes -
TUniMetaData data-types
the TUniMetaData data-type field now returns different data for different databases - Example:
currently for MySql it returns a string e.g. 'float'
but for MS SQL server it returns a number: e.g. 5 (for float fields)so the recommended improvement is to add a new field to the result that returns a string representing the native database type.
this feature is useful if you want to show a list of columns including data-types to the user - it can also be used to generate a create script, etc.
6 votes -
More control on Connection Pooling in Unidac Components
Timeout for connection pooling is fixed for 30000 ms in Unidac ( It is a local constant variable). It is not enough for some applications. We need more control on connection pooiling. It would be better if developer could set timeout as a property.
6 votes -
Support for Oracle objects in UniDAC queries.
Enable retrieving Oracle objects and varrays from database in query fields. Now in some cases it only properly works if you're retrieving object into a parameter.
6 votes -
TUniSqlMonitor - дозапись в файл
RUS
Предлагаю добавить у компоненты TUniSqlMonitor возможность указать имя файла, чтобы компонента сама всё писала в этот файл. Без использования события OnSQL.ENG
I propose to add a component TUniSqlMonitor the ability to specify the file name to the component itself is all written in the file. Without the use of event OnSQL.5 votes -
UNIDAC to support multiple connection pools in one application
It would be great if UNIDAC could allow the use of multiple connection pools. For example I need two connetion pools to 2 different databases at the same application. This is currently not supported in UNIDAC
4 votes -
Simple Example Code for the components
Put some simple sample code into the help/demos files, that must be great. some times that be very usefully
4 votes -
csv
Dar soporte para archivos csv
4 votes -
4 votes
-
Properties From MyDAC
It would be Nice to have implementation of:
- TUniQuery.CommandTimeOut
- TUniQuery.Options.NullForZeroDate4 votes -
They should have a component that imports data from excel, csv, or text into a table and that supports large files.
They should have a component that easily imports data from excel, csv or text into a table and that supports large files.
4 votes -
"DEFAULT VALUE" constraint support in TUniLoader
For now, if some of the data I need to load in db I'm not able to calculate all fiellds values, there's no way to indicate TUniLoader to let the DB Server apply the fields "DEFAULT VALUE" constraint if any.
A good way could be to make TUniLoader able to see no value (nor Null) was given to a column (so, still in "Unassigned" state).4 votes -
4 votes
-
4 votes
-
dbMonitor and TUniQuery - final SQL without parameters
dbMonitor
Please add another tab next to the tabs "SQL, Parameters, Error, CallStack" e.g. "Final SQL" in which we would be able to see SQL query with real parameter values instead of parameter placeholders ":Param1, Param2,...".
Please show real value of MEMO fields (TEXT - PostgreSQL, BLOB SUBTYPE 1 - Firebird, etc.) in parameters tab instead something like <BLOB:xxx>.
For real BLOB types (BLOB SUBTYPE 0 or BINARY) you can leave <BLOB:xxx>
TUniquery
Please add some property (like FinalSQL) but with real parameter values instead of parameter placeholders ":Param1, :Param2,...", so we can see actual SQL when debugging from Delphi…
3 votes -
dbMonitor shows string fields as <BLOB:19> Should show the actual data
dbMonitor, which is a great feature, shows any string values as <BLOB:19> instead of the actual data in that field. This might only apply to postgresql
3 votes -
Manually parse SQL for MBCS strings
Manually parse SQL for MBCS strings.
Latest UniDac MBCS specification is not full compatible with BDE/DBX(Delphi Ansi version).
and issue parse exception by mistake and macro function character at not ParamCheck.
and this exception is difficult to understand the cause.
(I have send details to support already)Please add the following property/Event.
- SkipParseSQL property
- OnBeforeParseSQL
- OnSQLParseError
3 votes
- Don't see your idea?