|
|
| | 10 | 15-APR-19 |
| | 10 | 29-JUN-18 |
| 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 |
| | 10 | 09-MAR-16 |
| | 9 | 05-NOV-15 |
| | 10 | 19-AUG-15 |
| | 10 | 14-MAY-15 |
| | 9 | 19-FEB-15 |
| | 10 | 18-AUG-13 |
| | 4 | 23-JUL-13 |
| This is very useful | 10 | 04-MAR-13 |
| Generation of Package API for each table would be very useful. | 8 | 17-JAN-13 |
| | 10 | 18-FEB-12 |
| This would be awesome! | 10 | 15-DEC-11 |
| | 9 | 12-OCT-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 |
| | 10 | 13-AUG-08 |
|
|
|