243 results found
-
Comment area on the Parameters tab
String parameters sometimes have special formatting forms, and it will be very useful to have a TMemo control to save a reminder on how the parameter should be formatted.
I mostly make use of String parameters to the TO_DATE function instead of DateTime parameters to avoid any conversion issue due to local Date and Time configuration.
It will be necessary to add a String property (Comment) to the TOraParam class to hold the comment data and add a TMemo control to the Parameters tab of the ODAC components (TOraQuery, TSmartQuery, TOraStoredProc and TOraSQL ) Editor.
1 vote -
Make a HELP SYSTEM for UniDAC more efficient and integrated IDE for RAD STUDIO
Create a more efficient system and connected to the Delphi IDE help. It seems that the team is out of date regarding the use of the Delphi help system, and, so far, not integrated their help file to the standard used by professional components for RAD Studio.
1 vote -
Option to let the user control the creation and maintenance of TRANSACTIONS manually, not automatic as with the current version (v5.5.12)
Many people do not bother with the beginning and ending a transaction, however, is of paramount importance to know when a good design to start and control your transactions.
Thus, it would be very interesting to have an option to control when the user wants to leave the components create or open a new transaction and when the user want and need to manually create your transactions.
So, a option to let the user control the creation and maintenance of TRANSACTIONS manually, not automatic as with the current version (v5.5.12)
1 vote -
Allow Joined tables' columns to be updated in TDBGrid, as ADO allows
When using TADOConnection / TADOQuery to create datasource for TDBGrid, columns from main tables as well as joined tables may be edited in the grid. With TUNIxxx components, only the first table in the query can have its columns updated in the grid.
1 vote -
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 -
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 -
Migration Wizard (Strip the .DB from tablenames if Paradox)
When converting from Paradox to SQLite, I ran into 2 problems.
1) the TableName.DB I used in paradox does NOT have a .DB ending in the actual tablename...
2) The data module where the "database1" was declared for the TUniConnection was not included in the files, and then the connections were not set to them. I had to open all the forms and remove the .db and set themI think that the Migration Wizard should handle those better...
1 vote -
Create driver/components to work with neo4j or orientdb
There are some great uses for graph databases and the Delphi desktop world would benefit greatly
17 votes -
The ability to create views with identical field names.
It will not take over the identical field names of a view. If multiple fields have the same name located in different sub-tables of this view.
1 vote -
include scheme as folows scheme.storedprocedurename in TUniStoredProc
Please include the scheme name of the stored procedure because now you have to include it manually, and if you dont it throws an error can find stored procedure, if i run MyStoredProcedure it throws an error but if i change it to MyScheme.MyStoredProcedure manually it works.
3 votes -
Optimization (move from config to compiler preprocessor)
Create means to eliminate overhead at the compiler or configuration level. Compiler would be better because it would have 0 overhead in the resulting app; whereas config would have to check if the area was desired.
The use case for me is that I have an app, 100% non-visual. It runs as a batch job. This app could/should be able to run faster if it didn't bother doing things that a non-visual app doesnt care about. ie - master/detail.
Most libraries I have seen have a configurable .INC which control what the behavior is at compile time. This would be…
2 votes -
Combine the IDE menus for the DAC products to be under one Devart menu as sub menus.
With all the different DAC products, I don't have space in my IDE for all the pull down menus. Especially since I have RemObjects, GExpers, MMX, etc, etc. It would be more optimal to have one single DevArt pull down menu in the IDE and then have a submenu for each DAC product.
3 votes -
Add property AutoStartTransaction
To control the implicit transaction
4 votes -
How about including a version of Entity Developer?
Entity developer would be a great addition to Rad Studio for use with PGDac. Either with code generation, or just as a DB design tool.
1 vote -
MyBackup
Backup procedure takes lot of time.
And user have no visual response. In large databases it takes minutes.
Why there is no OnProgress event to visually show estimated time with progress bar ?8 votes -
Add support for asynchronous queries for MySQL based on i/o completion ports technology
There is no Delphi solution for accessing MySQL database optimized for performance on heavy loaded servers.
12 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 -
TMyTable - Please add SORT function :-(
I'm cobnverting from ADO to MyDac...and the tables don't have a SORT function.
1 vote -
Display Computed fields values and exclude from SQL Generator
I really like to see a new option in the TIBCQuery component to display the computed field automatically like the option defaultvalues
Also to exclude all the table computed fields from insert and update SQLs automatically when using the SQL generator tab in TIBCQuery so I dont get errors about modifying read only dataset
This small enhancement but will boost development time
thanks
Seems8 votes -
Eliminate parethesis when using AddWhere
I would like complete control on how the parenthesis are added to the where clause. The way they are added now, it can result in a where clause that won't return what you're looking for.
1 vote
- Don't see your idea?