How to exclude tables from SchemaExport?

h.b. · **Joined:** Wed Apr 13, 2005 10:34 am **Posts:** 38

Is it possible to exclude mapped tables from SchemaExport/Update? For example tables that are replicated or shared between several applications.

Regards,

Heiko

h.b. · **Joined:** Wed Apr 13, 2005 10:34 am **Posts:** 38

I'd like to bring the Topic back to top.
Obviously there is no such feature yet?

It would also be useful for tables only accessible via database links and in combination with the schema validation function available in 3.1.

MartinLeim · **Joined:** Tue Jul 26, 2005 6:26 am **Posts:** 15

If you specify that your class is abstract (even if it actually isn't), no table is generated. I don't know, if this has results on other things, but you could give it a try.

max · **Posted:** Tue Jan 10, 2006 3:50 pm

such a feature is not implemented (yet)

Might be relevant to do at some point - patches welcome.

h.b. · **Joined:** Wed Apr 13, 2005 10:34 am **Posts:** 38

MartinLeim wrote:

If you specify that your class is abstract (even if it actually isn't), no table is generated. I don't know, if this has results on other things, but you could give it a try.

Thanks, but making the class itself abstract is not an option. I need instances of this class.

I also tried mapping the class as abstract but it has no influence on SchemaExport.

marw · **Posted:** Fri Aug 25, 2006 7:37 am

Just an idea:
Excluding mappings from schema generation could be implemented by using a <meta>-attribute that tells SchemaUpdate/SchemaExport to not generating the DDL.

max · **Posted:** Fri Aug 25, 2006 7:40 am

won't work.

one class != one table