Package Error when create package via Methods onTables

Question

Even though I am an APEX developer for 3 years, I just found out about Methods on Tables Utility in SQL Workshop from Dan McGhan's demo. I tried to create a package for about 7 tables in one package. When the package was created, it was invalid. I tried to compile it and it produced several errors. I noticed that the UPDATE table procedure was incomplete as it did not provide parameters even though the procedure uses them.
I was able to replicate it in APEX.ORACLE.COM.
WORKSPACE: RGWORK
PACKAGE: CSRSR_DML
USER : TESTER
Password: test123
Is this a bug? Is there a workaround? Did anyone else experience similar outcome?
APEX 4.1
Oracle 10g Rel 2
Robert
http://apexjscss.blogspot.com

Answer 1

sect55 wrote:
Come on APEX team and gurus, please help....As far as this "guru" is concerned, it's not something I'd ever use:
http://asktom.oracle.com/pls/apex/f?p=100:11:0::::P11_QUESTION_ID:672724700346558185
http://asktom.oracle.com/pls/apex/f?p=100:11:0::::P11_QUESTION_ID:25405782527721
Given Tom's well-known opposition to this approach, I was more than a little surprised when this appeared in APEX as he also appears to have close links to the APEX team. I'd really rather have seen development effort invested elsewhere.
I'd definitely advocate building applications based on PL/SQL APIs, just not on table-centric, row-by-row ones...
I tried to create a package for about 7 tables in one package.Why?
One of the main purposes of packages is to modularize an application. Sticking methods for all of the entities in one package defeats this and makes development, testing and maintenance harder. If you must use the flawed TAPI concept, create a separate API for each table&mdash;at most only combine those where there exist mandatory dependencies, e.g. an <tt>order</tt> package with methods for <tt>orders</tt> and <tt>order_items</tt>.
As to the immediate problem, it appears to be due to the lack of primary key definitions on some of your tables. This means the generator is unable to identify which columns to use as unique row identifiers.