Posts
Why a Table API? Well, some teams would never dream of letting developers insert, update , delete or generally work directly with tables. Many teams want to track who, what, when, where events and having a Table API (I call them "table wrappers") is a start point to add in that kind of code. Here's how you'll find it:
3 comments:
This is a very good an close to what I would like to see. An important change would to create a SUBTYPE in the package as follows:
SUBTYPE TABLE_NAME_row is TABLE_NAME%rowtype;
Then reference the subtype in the parameters instead of each individual column. This will greatly reduce the impact of table changes in other code.
NOTE: when returning the subtype as a procedure parameter it should be declared with NOCOPY!
Hi,
Thanks for the feedback - all product requests should be posted on the SQL Developer Forum on OTN for discussion:
http://forums.oracle.com/forums/forum.jspa?forumID=260
Sue
Nice, but I was expecting something near to what ORACLE designer generates for TAPI.
Post a Comment