You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ddlutils-dev@db.apache.org by "Thomas Dudziak (JIRA)" <ji...@apache.org> on 2006/04/09 20:38:23 UTC
[jira] Updated: (DDLUTILS-87) Add ability to specify which tables
to include/exclude when reading a model from the database
[ http://issues.apache.org/jira/browse/DDLUTILS-87?page=all ]
Thomas Dudziak updated DDLUTILS-87:
-----------------------------------
Summary: Add ability to specify which tables to include/exclude when reading a model from the database (was: Did not filter out system table dtproperties.)
type: New Feature (was: Bug)
Environment: Any database (was: SQL Server 2000.)
Priority: Major (was: Minor)
Changed the issue to more accurately reflect the problem at hand. For instance, dtproperties is not a system table (i.e. it is a normal table of type TABLE), so DdlUtils cannot really know that it is a system table. Hence, it makes sense to add the ability to define include and exclude patterns that specify which tables to read from the database.
> Add ability to specify which tables to include/exclude when reading a model from the database
> ---------------------------------------------------------------------------------------------
>
> Key: DDLUTILS-87
> URL: http://issues.apache.org/jira/browse/DDLUTILS-87
> Project: DdlUtils
> Type: New Feature
> Components: Core
> Environment: Any database
> Reporter: Jun Li
> Assignee: Thomas Dudziak
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira