Fast Report in Lazarus frxODACComponents is not included in the set of our componente when using the Lazarus environment58 votes
Add possibility to work with с XML data type as with CLOB.27 votes
Add new property FlatADTView (default false for not changing standard behavior of TOraQuery) for showing fields separately in ftADT field in Object View mode.
CODE: SELECT ALL
create or replace type ComplexType as object(
OraQuery1.SQL.Text := 'select ComplexType(CODE, name) A from TEST';
OraQuery1.ObjectView := True;
OraQuery1.FlatADTView := True; (new property)
And I want to see:
CODE: SELECT ALL
A.X | A.Y
1 | 2
3 | 4
like OraQuery1.ObjectView := False but this variant friendly for collections datatype.25 votes
Add a way to turn off active sorting without losing the current sort order (ODAC lost this feature.)
ODAC has always allowed clearing IndexFieldNames without reverting to the original sort order. The ability to sort a dataset and then turn off active sorting is very useful (and necessary for editing a sorted dataset in a grid component.)24 votes
It is very important nowadays in using oracle cloud services, which require using the oracle Wallet, especially for ADW and ADT.13 votes
I would like to use complex connect strings similar to JDBC thin driver, e.g.
It is similar to the entries you can put into the TNSNAMES.ORA file.
It looks like ODAC.net does support something similar,
I would like to have it in the VCL version.
To us, the most important thing is Connect Time Failover9 votes
Add support Transaction Guard (Oracle 12c New Feature) in ODAC8 votes
Add an option into the session object to deactivate the "
begin :result := sys.dbmstransaction.localtransaction_id(true); end; " calls.7 votes
Add 2 new String properties to TField containing text used for SQLInsert/SQLUpdate statements.
This allow using SYSDATE or subselects without need of consructing whole SQLInsert or SQLUpdate. Property can be emptystring or null by default.4 votes
Add Async notifications support to OraQueue in Direct mode.4 votes
Currently, the function TOraNumberField.GetAsVariant returns a variant of String type:
Result := AsNumber.AsString;
As a result, data accessed by AsVariant method cannot be processed numerically with 3rd-party data bound components such as DevExpress TcxGridDBChartView.
A change like this or similar would do:
Result := AsNumber.AsFloat;
on E: Exception do
Result := variants.null;
It allows data to be displayed in Devexpress chart views that read numeric data as variant.3 votes
I would like it to have a record limit setting that is the same or similar to what exists in FireDAC.
This configuration and the behavior of FireDAC with this configuration would be nice to have in the Devart ODAC component.
Here is an example of what exists in FireDAC:
TFDQuery.FetchOptions.RecsMax := 100;3 votes
Change TOCICommand.InitProcParams7 MaxParams constant to 2503 votes
At execproc runtime call when this option is checked and the value of the parameter is null display a warning message.
When "mandatory" is not checked nothing is done and the component workd like before.
The principe is a bit like "assertions" in code ... we want to make sure that parameters required by procedures are filled by programmers and not forgotten.
Those who don't want the feature can just ignore it.
The concept could be extended to an assertion formula, but for us a checkbox is enought1 vote
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
- refresh record;
- QBE mode on/off;
- run QBE.1 vote
- Don't see your idea?