| routine editor bug [message #583451] |
Mon, 11 December 2006 17:19 |
 Francine Grimmer
Messages: 17
Registered: July 2009 |
Junior Member |
|
|
I am seeing a new problem in DTP 1.0. When I try to 'run' a stored
procedure that has in and out paramters, the 'popup' for entering the data
for the in and inout paramters is also displaying the out paramters. These
should not be displayed in this 'popup' as users should not enter data
into the out paramter. This problem is also seen when connected to Derby
as well.
The problem is that the LaunchUI class was changed to check the paramType
by comparing it to database metadata values instead of the ParameterMode
value, when ignoring output type values. It used to ignore
ParameterMode.OUT, but now it ignores database metadata values Unknown,
ColumnResult, and ColumnReturn. For our database (Teradata) a stored
procedure out parameter is stored as a parameterOut. It fails to also
include ParameterOut in this list.
Also, why are we going back to the database for this information
(ParameterUtil.getParameterDescriptors())? We have already gathered this
information and stored it in the Routine parameter list. This is an
unnecessary hit on the database. This is causing another problem in that
we have other Routine objects (Macros) that extend from Routine that also
have input paramters. And now in DTP 1.0, trying to 'run' these routines
is failing to gather the input paramter data because the parameter data is
not returned in the database metadata.getProcedureColumns. We need some
way to go back to getting this information from the routine parameter list.
-francine
|
|
|
Powered by
FUDForum. Page generated in 0.04011 seconds
] 
Search
Help
Register
Login
Home
