I'm looking to exclude as many columns out of the reveng as possible. Why? I [b]really[/b] like the reveng capabilities of Hibernate tools, but it does create a very tight coupling to the database I'm using (a db which has a lot of data / columns that I'm not interested in). I'm afraid that over time, new columns (that I'm not using) will be added and changed to the tables in the db, and at some point my app will break due to the tight coupling I get from reveng.xml.

Thus, I'd like to have this construct:
<table name="X">
<column name="INTERESTING" exclude="false" />
<column name=".*" exclude="true" />
</table>

This way, if someone adds a column, then at some later point changes or deletes it (and somewhere in the middle of this I'd reveng'd off an intermediate schema), my app would remain unaffected by any such changes.

BTW, this is what I'm doing today:
<table name="X">
<column name="INTERESTING" exclude="false" />
<column name="NOT" exclude="true" />
<column name="VERY" exclude="true" />
<column name="RELAVENT" exclude="true" />
</table>

If there's a way I can bulk exclude columns (ala column name=".*"), let me know. Otherwise, please consider this as a future enhancement.

hmm....it would be possible via custom revengstrategy impl if excludeColumn returned a Boolean instead of a boolan.

then you could just return true for those columns/tables the delegate doesn't know.

put it in jira with a ref to this forum posting and i'll consider what we can do.

Hi, do you have more information about

<column name=".*" exclude="true" />

I try to use this syntax, but Hibernate generates code for all the table columns.

column=".*" is a suggested improvement - i don't recall any jira/patches about it yet.