Choose a layout and drag widgets onto your Overview Page to customize it. Widgets placed on the page below can be configured by selecting the symbol.
Click here to view all ideas!
Currently, DBCA creates all datafiles as smallfile tablespaces. This can be manually changed when generating the scripts (-generateScripts) by adding SET DEFAULT BIGFILE in the CREATE DATABASE statement just before LOGFILE GROUP A command line option would be nice, something like useBigFile <true | false > which defaults to false but can be set to true.
There are some Oracle tools and third Party tools that allows Create a User as another one but we still don’t have this possiblity writing just SQL Code I’d like to have a New Clause “as User” in Create User for example Create User ... as User ... Identified by ... this clause have to recover the user definition (default tablespace, temp, profile, etc) and privilegies from the originary user and create a New user with the same definitions and Grant the same privileges
The dbms_lob is too complicated for a supported type. It should be natively supported. declare longString CLOB; longString2 CLOB; begin longString := '456465...asdfsdf'; -- past the current VARCHAR2 limit longString2 := substr(longString, 500000 /*Start Index*/, 400000 /*length*/); ... end; Having a native support would allow to easily move from VARCHAR2 to CLOB when required. Currently this process is painful.
Support for the foreach. PHP: foreach - Manual This greatly simplifies the code for a loop on collection type. declare type t is table of integer index by varchar(32); v t; begin v(1) := 1000; v(2) := 2000; v(4) := 3000; v(5) := 4000; foreach (v as v_index => v_value) loop htp.p(v_index || ': '|| v_value); htp.br; end loop; end; This will output in the htp output 1: 1000 2: 2000 4: 3000 5: 4000 No need to check if the index exists.
In static DML embedded in PL/SQL, if the RETURNING INTO clause is used to populate values in a record, the columns returned must match exactly the order of the attributes of the record. If the record is based on a %ROWTYPE (e.g. for a table or a view), the results are unpredictable depending on the order of the columns in the table that the rowtype is defined on. For example: create table parts (part_number number primary key, part_name varchar2(100), part_type varchar2(100)); insert …
No user featured