Re: Oracle 11g new features

On Mar 25, 8:31 am, sybra..._at_hccnet.nl wrote:

> On Wed, 21 Mar 2007 20:49:29 +0100, "Matthias Hoys" <a..._at_spam.com>
> wrote:
>
> >How about:
>
> >CREATE USER LIKE ...
> >FLASHBACK SCHEMA ...
> >select * from v$alertlog (ok, this one can be easily made with external
> >tables :-))
>
> >Matthias
>
> I would wish Oracle would
> - drop CONNECT, RESOURCE and DBA roles *completely*

As soon as they do, someone will post a .SQL script to recreate them. <g>

> - make it impossible to have a password equal to the username
> ( I know both can be done, but 99 percent of all third party app
> developers don't protect their databases and refuse to have the
> privileges and the password changed)

Probably strategic. Users value simplicity over security. This might be
of value to auditors, however, if Oracle does this, users will whine even
louder.

A few of the things I'd like to see for 11g (or future) would be

• stronger 'proxy user' capability for those connection-pool developers;
  • better docco around things like 'proxy user';
• better examples to avoid reinventing what Oracle has already invented;
  • not drop Workflow (see above point);
• simplify existing features so they'll actually get used;
  • improve (create, actually) the Oracle Text admin interface;
  • more 'feature admin' OEM plugins (DBMS_EPG ports, spatial, WrkSpc);
  • ability/guidelines to create custom admin OEM plugins;
• Oracle sales actually knowing the features;
  • a weekly or monthly 30 minute 'know your features' webcast with demos;
  • a developer-oriented 'get value from Oracle with this feature...' cast;
• roll [more parts of] ASO into the database and more fully use OiD/ LDAP;
• apply synonyms to roles;
• ability to set the external table file name on the fly without DDL;
• init parms to set feature or operation usage/mode; (eg:)
  • init parm to kill public synonyms, (helps instance consolidation);
  • init parameter to kill 'GRANT UNLIMITED TABLESPACE';
• pluggable engines (eg: PERL) to run along side PL/SQL and Java;
  • make PL/SQL engine standalone;
• declaratively tie a sequence to a column as a constraint;
  • DBMS_EPG enhancements to more fully replace mod_plsql;
  • TIME datatype [hh(n):mi(m):sec(j)] to record duration (> 24 hours);
  • Does time series still exist?
• make the gosh-*&^(*(*%& database control a bit lighter weight;
• ability to read trace files as external tables;
  • statspack with more access to internal measurements;

And one for the screen developers who want to pass all fields, whether changed or not:

UPDATE table
SET col=value ...
SET_IF_CHANGED col=value ...

which (amongst other things) would not invoke triggers when the new=old.

(Don't get me started on App Server, Forms, Reports, etc. <g>)

--
Hans Forbrich   (mailto: Fuzzy.GreyBeard_at_gmail.com)
*** Feel free to correct me when I'm wrong!
*** Top posting [replies] guarantees I won't respond.