New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add option to disable views export from database #338

Closed
paplorinc opened this Issue Feb 4, 2013 · 5 comments

Comments

Projects
None yet
3 participants
@paplorinc

As I have mentioned in #337 (comment) I would like to have an option for the Maven config to disable any other exports, but database tables (eg. views, triggers, etc.), if possible.

Thanks,
Pap Lőrinc

@paplorinc paplorinc referenced this issue Feb 4, 2013

Closed

Oracle issues #337

@timowest

This comment has been minimized.

Show comment
Hide comment
@timowest

timowest Feb 4, 2013

Member

Ok, this is accessible via the TABLE_TYPE column and can also be specified in the getTables calls.

Maybe the default could be TABLE and VIEW, and via skipViews VIEW handling could be disabled.

Member

timowest commented Feb 4, 2013

Ok, this is accessible via the TABLE_TYPE column and can also be specified in the getTables calls.

Maybe the default could be TABLE and VIEW, and via skipViews VIEW handling could be disabled.

@timowest

This comment has been minimized.

Show comment
Hide comment
@timowest

timowest Feb 5, 2013

Member

The export scope can now also be controlled via the exportTables (default: true) and exportViews (default: true) options.

Member

timowest commented Feb 5, 2013

The export scope can now also be controlled via the exportTables (default: true) and exportViews (default: true) options.

@paplorinc

This comment has been minimized.

Show comment
Hide comment
@paplorinc

paplorinc Feb 5, 2013

Thank you Timo, beautiful work :)!

Btw, an insignificant remark: types.toArray(new String[types.size()]) is slightly better than types.toArray(new String[0])

Thank you Timo, beautiful work :)!

Btw, an insignificant remark: types.toArray(new String[types.size()]) is slightly better than types.toArray(new String[0])

timowest added a commit that referenced this issue Feb 5, 2013

@timowest

This comment has been minimized.

Show comment
Hide comment
@timowest

timowest Feb 20, 2013

Member

Released in 3.0.0.BETA2

Member

timowest commented Feb 20, 2013

Released in 3.0.0.BETA2

@timowest timowest closed this Feb 20, 2013

@khoran

This comment has been minimized.

Show comment
Hide comment
@khoran

khoran Feb 13, 2014

This change has broken the generation of classes for table returning functions and user defined TYPEs (in postgres). There are more then just tables and views in the world of databases. Can you please add an option to return the original functionality of generating classes for everything? Thanks.

khoran commented Feb 13, 2014

This change has broken the generation of classes for table returning functions and user defined TYPEs (in postgres). There are more then just tables and views in the world of databases. Can you please add an option to return the original functionality of generating classes for everything? Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment