After modeling is in place, it would be great to be able to generate customizable table APIs, similar to (but much simpler than the ones produced from Designer. Primarily to implement a standard framework for custom PL/SQL DML and business rule implementation either at the trigger level and/or as a specific and standard package call. SUe will know what I mean here.
Most of the power of Designer for server-side development can be recovered with this additional feature to SQL Developer somewhere in the 2.0+ release.
|We still use Oracle Designer because we need this feature.||10||24-APR-18|
|A must have!||10||01-MAR-18|
|We still use ORACLE CDM (custom development methodology)
for implementing business rules within a table API. This way, business rules are checked no matter what input program is used, whether a custom application in Forms, JDeveloper, SQLPlus, Toad. Still very usefull but Designer has been obsolete since .... ||10||22-SEP-16|
|This is very useful||10||04-MAR-13|
|Generation of Package API for each table would be very useful.||8||17-JAN-13|
|This would be awesome!||10||15-DEC-11|
|When choosing for this approach, generating TAPI's based on a model would be a valuable feature.||10||11-MAY-11|
|The absence of generated table APIs is probably the primary reason why we're still using Designer instead of the Data Modeler.
I'd prefer TAPIs to be available from within the core SQLdeveloper product.||10||25-APR-10|