RDBPROD: How to handle sql injection risks in Oracle Rdb v7.2
As far as we know this is best done by using stored procedures. Is this correct?
If so, how do we return record sets to the calling system? We have been looking around for answers and it seems like it is possible to solve, not directly, but with a workaround to simulate cursors; however we cannot get it right mainly on the calling side to loop (and fetch) records until end of stream.
Best regards,
Owe Fanqvist