Enhancement Request - TableWindow - View (DDL) - with/without (storage/ts-clause)

[orca777]

Hi DevTeam,
would it be possible to generate the DDL of Tables completly without storage/tablespace-clause?

Instead of :

create table ACTIVITY
(
  ID         RAW(16) not null,
  COMPANY_ID RAW(16) not null,
  NEXT_ID    RAW(16),
  PREV_ID    RAW(16)
)
tablespace USERS
  pctfree 10
  initrans 1
  maxtrans 255
  storage
  (
    initial 64K
    minextents 1
    maxextents unlimited
  );
-- Create/Recreate primary, unique and foreign key constraints
alter table ACTIVITY
  add constraint ACTIVITY_PK primary key (ID)
  using index
  tablespace USERS
  pctfree 10
  initrans 2
  maxtrans 255
  storage
  (
    initial 64K
    minextents 1
    maxextents unlimited
  );
alter table ACTIVITY
  add constraint ACTIVITY_NEXT_FK foreign key (NEXT_ID)
  references ACTIVITY (ID);
alter table ACTIVITY
  add constraint ACTIVITY_PREV_FK foreign key (PREV_ID)
  references ACTIVITY (ID);
-- Create/Recreate indexes
create index ACTIVITY_NEXT_FK on ACTIVITY (NEXT_ID)
  tablespace USERS
  pctfree 10
  initrans 2
  maxtrans 255
  storage
  (
    initial 64K
    minextents 1
    maxextents unlimited
  );
create index ACTIVITY_PREV_FK on ACTIVITY (PREV_ID)
  tablespace USERS
  pctfree 10
  initrans 2
  maxtrans 255
  storage
  (
    initial 64K
    minextents 1
    maxextents unlimited
  );

this output (with a checkbox near the view window?)

create table ACTIVITY
(
  ID         RAW(16) not null,
  COMPANY_ID RAW(16) not null,
  NEXT_ID    RAW(16),
  PREV_ID    RAW(16)
)
;
-- Create/Recreate primary, unique and foreign key constraints
alter table ACTIVITY
  add constraint ACTIVITY_PK primary key (ID)
;

alter table ACTIVITY
  add constraint ACTIVITY_NEXT_FK foreign key (NEXT_ID)
  references ACTIVITY (ID);

alter table ACTIVITY
  add constraint ACTIVITY_PREV_FK foreign key (PREV_ID)
  references ACTIVITY (ID);

-- Create/Recreate indexes
create index ACTIVITY_NEXT_FK on ACTIVITY (NEXT_ID)
;
create index ACTIVITY_PREV_FK on ACTIVITY (PREV_ID)
;

Very often i test code between different databases different tablespaces or i want just to post some ddl in blogs and always i have to put away the storage manually :-(

With kind Regards
Carl r.

 

[Helene]

Yes, please!

BUT in addition, I would like to also be able to leave out everything else, but keep the tablespace specification. This is because we always have all indexes in a tablespace different from the tablespace for tables.

Helene

 

[CTzen]

What Helene said I need those tablespace names as well without actual storage parameters.

Please

 

[Marco Kalter]

The "export user objects" and "export tables" tools have an "Include Storage" option. I have added your request for an "Include Tablespace" option to the list of enhancement requests.

 

[orca777]

Originally posted by Marco Kalter:
The "export user objects" and "export tables" tools have an "Include Storage" option. I have added your request for an "Include Tablespace" option to the list of enhancement requests.

Hi Marco,
its important to mention to include the functionality in the Table-window (VIEW SQL) itself this a lot faster to work then an a table export.
Aggree totaly with Helen & CZten to allow a mode with tablspace clause only.

With kind regards
Carl

 

[Helene]

Hi,
I agree that this is also needed in the VIEW SQL window, this is actually the one we use. I have never even tried the "export user objects/export tables" functions!

With regards,
Helene

 

[Helene]

Hi,

Any news on this request ?

With regards, Helene

 

[Marco Kalter]

It is planned for 7.1 later this year.

 

[orca777]

Great!
Karl

 

[Helene]

When can we expect this to be delivered?

I also have another issue, which should be very easy to fix, and which would really mean very much to us. So please... provide an option to include the owner in all DLL which is generated! This is necessary both in the VIEW SQL window, and not least in the program windows.

We store all trigger and package definitions with the schema name specified, but every time we use PL/SQL developer to edit them, it is stripped off again... quite frustrating, as all files need to be manually edited after saving them!

With regards, Helene

 

[Marco Kalter]

Version 7.1 is scheduled for the end of this year.

 

[Marco van der Linden]

Would make a nice Christmas present

 

[sukhadukkham]

would it also be possible to apply the keyword case defined in preferences=>editor to this?

 

[Marco Kalter]

I have added this to the list of enhancement requests.

 

[Helene]

I am really really looking forward to this relase

with regards
Helene

 

[Helene]

Hello,
and a very happy new year!

7.1 was scheduled for the end of last year, have you got any news for us about this version ?

With regards,
Helene

 

[Marco Kalter]

Happy new year to you too.

7.1 has been delayed a little bit, but we hope to have a beta out shortly.

 

[Helene]

Are any of these enhancements included in the 7.1 Beta?

I have tried to find a way to include the owner in the generated DDL, but haven't found it so far?

With regards, Helene

 

[Marco Kalter]

This is not yet in the current beta.

 

[orca777]

Would be nice to have ;-)
Karl

 

[Helene]

This is actually the ONE thing that I am really, really waiting for!

This, and an option to save the program code with the owner schema name intact - now it is automatically removed. (E.g. "create or replace package MYSCHEMA.mypackage" - when compiled in the schema MYSHCEMA, this is automatically transformed into "create or replace package mypackage").

With regards, Helene

 

[Helene]

What is the status of this request for version 8.0 ?

 

[Marco Kalter]

It has not been implemented in 8.0.0, but is still on the to-do list.