[
https://issues.apache.org/jira/browse/DDLUTILS-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Dudziak resolved DDLUTILS-87.
------------------------------------
Resolution: Fixed
The databaseToDdl task now has four additional attributes, includeTables &
includeTableFilter and excludeTables & excludeTableFilter, that allow to
specify which tables to include and exclude (as a comma-separated list or a
regular expression). Includes are evaluated first, then excludes. If there are
foreign keys between tables that are included and tables that are excluded
(whether explicitly or not), then the task will fail.
> Add ability to specify which tables to include/exclude when reading a model
> from the database
> ---------------------------------------------------------------------------------------------
>
> Key: DDLUTILS-87
> URL: https://issues.apache.org/jira/browse/DDLUTILS-87
> Project: DdlUtils
> Issue Type: New Feature
> Components: Ant Tasks, Core (No specific database)
> Environment: Any database
> Reporter: Jun Li
> Assignee: Thomas Dudziak
> Fix For: 1.1
>
> Attachments: DDLUtils-TableNameRegExpFilter.patch
>
>
> On SQL Server dtproperties is a system table.
>
> But DdlUtils did not filter it out like it does for other system tables like
> syscolumns, sysfiles, sysindexes, and so on.
> Some people reported that it's also a issue in PostgreSQL 8.1
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
