Opened 15 years ago
Closed 15 years ago
#1141 closed defect (fixed)
Feature Service API: Out parameter are not working
Reported by: | Aleck | Owned by: | Aleck |
---|---|---|---|
Priority: | low | Milestone: | |
Component: | General | Version: | 2.0.2 |
Severity: | trivial | Keywords: | |
Cc: | External ID: |
Description
In feature service API MgFeatureService::ExecuteSqlQuery and MgFeatureService::ExecuteSqlNonQuery methods, there is an argument for parameter binding. The parameters for a sql statement can be an output parameter. However, the client can't get the value of out parameters after executing the sql statement. This is because current server structure does not allow out parameters.
Therefore, the solution is to create an intermediate object MgSqlResult which contains a !rowUpdated integer, an MgParameterCollection and an MgSqlDataReader object. Once the ExecuteSqlQuery or ExecuteSqlNonQuery operation is finished, the intermediate MgSqlResult object will be serialized. The ProxyFeatureService will deserialize the MgSqlResult and process the value of out parameters.
Attachments (1)
Change History (3)
by , 15 years ago
Attachment: | patch1.patch added |
---|
comment:2 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
PATCH