| routine editor bug [message #24188] |
Mon, 11 December 2006 12:19  |
Eclipse User |
|
|
|
Originally posted by: francine.grimmer.ncr.com
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
|
|
|
| Re: routine editor bug [message #24285 is a reply to message #24188] |
Wed, 13 December 2006 00:53  |
| Eclipse User |
|
|
|
Hi Francine,
The out parameter problem has been solved in 158248. The Parameter
Configuration dialog will ignore procedureColumnOut as well now.
SQL Dev Tools uses JDBC metadata values instead of ParameterMode
because: 1, JDBC metadata provides more types other than in, out, and
inout; 2. we need to know other information of the Parameter, such as
nullable and defaultValue, which is logged in 129326, and will be fixed in
DTP 1.5.
For now, you can override SQLObject.getParameterDescriptor() to handle
your Macro objects.
Regards,
Hui Cao
Francine Grimmer wrote:
> 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
|
|
|
| Re: routine editor bug [message #583474 is a reply to message #24188] |
Wed, 13 December 2006 00:53 |
| Eclipse User |
|
|
|
Hi Francine,
The out parameter problem has been solved in 158248. The Parameter
Configuration dialog will ignore procedureColumnOut as well now.
SQL Dev Tools uses JDBC metadata values instead of ParameterMode
because: 1, JDBC metadata provides more types other than in, out, and
inout; 2. we need to know other information of the Parameter, such as
nullable and defaultValue, which is logged in 129326, and will be fixed in
DTP 1.5.
For now, you can override SQLObject.getParameterDescriptor() to handle
your Macro objects.
Regards,
Hui Cao
Francine Grimmer wrote:
> 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.03701 seconds
Home