Then I try to change
TOraQuery.SQL.text at runtime (for execute query with stored procedure),
I can access any parameter of this procedure, it's correct.
But type of any parameter is ftUnknown, it's not correst!
However, in design-time, then I put my SQL into TOraQuery, parameter's DataType recognized correctly.
How can I get correct DataType of parameters after changing SQL at runtime?
Thanks.
Changing OraQuery.SQL.text at runtime and incorrect param DataType ftUnknown after...
To make ODAC automatically detect data type for stored procedure parameters, you should use the TOraStoredProc component.
When you set the SQL property for the TOraQuery component, the DataType property for all parameters is set to ftUnknown. But DataType of parameters that was present in previous SQL text remains unchanged.
Please provide us a sample demonstrating the problem: value of the SQL property before and after the change, and data types of parameters before and after the SQL property has been changed.
When you set the SQL property for the TOraQuery component, the DataType property for all parameters is set to ftUnknown. But DataType of parameters that was present in previous SQL text remains unchanged.
Please provide us a sample demonstrating the problem: value of the SQL property before and after the change, and data types of parameters before and after the SQL property has been changed.
I understand my mistake.
Sorry.
I understand my mistake.
I tried to use PL/SQL block with stored procedure call in TOraQuery SQL, but TOraQuery can’t retrieve DataType of parameters in this case, like TOraStoredProc (may be SELECT ... FROM ALL_ARGUMENTS WHERE ... or any other way).
However, may be it's good to add this functionality to TOraQuery with PL/SQL stored procedure call in the future.
I understand my mistake.
I tried to use PL/SQL block with stored procedure call in TOraQuery SQL, but TOraQuery can’t retrieve DataType of parameters in this case, like TOraStoredProc (may be SELECT ... FROM ALL_ARGUMENTS WHERE ... or any other way).
However, may be it's good to add this functionality to TOraQuery with PL/SQL stored procedure call in the future.