Page History

...

Image RemovedImage Added

The element in question here is a basic grid, let's click into it.

Image RemovedImage Added

The grid is using a pair of identical load and store binder (which makes sense most of the time so that data is stored and loaded from the same source). We can opt to use JDBC Binder as the load binder so that we can gain full control on how dataset is returned and constructed.

...

select c_name, c_quantity, c_price, c_parentrequest_id from app_fd_purchase_items where  c_parentrequest_id = ?
union
select "SUM", sum(c_quantity), sum(c_price),  c_parentrequest_id from app_fd_purchase_items where  c_parentrequest_id = ?

And this is a sample result by running them on a command line interface.

...

+--------+------------+---------+---------------------------------+

| c_name | c_quantity | c_price |  c_parentrequest_id                              |

+--------+------------+---------+---------------------------------+

| pen    | 1          | 10      | 1177_purchaseRequition_purchase |

| pencil | 2          | 20      | 1177_purchaseRequition_purchase |

| SUM    | 3          | 30      | 1177_purchaseRequition_purchase |

+--------+------------+---------+---------------------------------+

Image RemovedImage Added

However, it does not actually play out well with the JDBC Binder as it is only expecting one parameter in the query. Our union query has 2 parameters.

...

DELIMITER //
CREATE PROCEDURE purchase_items_dataset
(IN recordId CHAR(255))
BEGIN
  select c_name, c_quantity, c_price,  c_parentrequest_id from app_fd_purchase_items where  c_parentrequest_id = recordId
union
select "SUM", sum(c_quantity), sum(c_price),  c_parentrequest_id from app_fd_purchase_items where  c_parentrequest_id = recordId;
END //
DELIMITER ;

...

Image RemovedImage Added

This is the outcome.

Image RemovedImage Added