Define tablespace for indexes and special columns

[rainald.riedel]

I think the following feature does not yet exist. If I am wrong, please tell me:
I would like to define a tablespace not only for tables in ORACLE databases, but also for indexes and special fields of the table, namely for BLOB-fields.

[Steve_Ferry]

I am starting a project and I trying to gey as much DDL exported as possible. So far I have failed to get the tablespace added to the Oracle DDL.

[«Midnight»]

It is a tagged value. See "Set Oracle Table Properties" in help - as of build 816. [It might have been as of one or two builds earler, but it is definitely in help for 816.]

Note that there is also a new Tablespace property of Element in the API. It is for this purpose.

I don't believe this value can (yet) be set for things other than tables. You might want to make a suggestion regarding this directly to Sparx. If so, check my recent posts for a best practice to do this and share with the forum community.

David

[Steve_Ferry]

Thanks for this it has been very useful. I have now found a lot of the Oracle specific database bits and pieces I was looking for.

It does almost all of the SQL I was hoping for.

I am adding tables to an existing schema for my current project. I have on my diagram some tables that alreay exist and some new ones. Is there a way of marking tables so they do not automatically generate table create SQL. I need these tables for some of the FK constraints I am adding.

[«Midnight»]

I don't know if you can do this directly. Here's a couple of suggestions that might make your life easier.

You could move the tables you've already done into a different package, but keep references to them in your diagrams. Just drag them to the new package in the Project Browser view. You might want to change a couple of options in the diagram options dialog (F5). Look at Show Additional Parents (and Highlight Foreign Elements in earlier versions of EA). When you generate package DDL you should now get DDL for only the 'new' elements.

You could also assign a different Status to new and old tables in the Properties dialog. [Remember, you can create your own status codes via the Settings | General Types dialog, and you can move these between projects via Export/Import Reference Data.] This will allow you to color tables according to status if you turn that option on with the Tools | Objects | Show status colors on diagrams option. However, in order to restrict DDL generation you'll probably need to write an add-in.

HTH, David

[Steve_Ferry]

I have tried the first option and it has worked. This will save me a great deal of time. Thanks.

[lauriechan]

hi,
does anyone know if there has been any progress in regard to this issue since last year or can suggest workarounds?

I'm using v7.1 build 827 and haven't found a way to coerce EA into generating either:
 - the "USING INDEX TABLESPACE" clause for primary key constraints
 - the "LOB() STORE" clause for tables containing BLOBS


Laurie