-
Bug
-
Resolution: Done
-
Major
-
7.4.2
-
None
When importing a DDL file, the importer fails. Its hard to determine where the problem is in the file. It was suggested it would be nice if it could parse what it can and then indicate after which statement it failed.
Also, it would be nice to be able to select which objects (like the jdbc importer of selecting tables, indexes, etc.) to import. Maybe the ddl importer could utilize part the jdbc importer wizard to provide the same options.
- clones
-
MODE-1326 Oracle DDL Parser throws exception parsing CREATE UNIQUE INDEX
- Closed
- relates to
-
TEIIDDES-1739 Refactor DdlImporter into dialect-specific processors.
- Closed
-
TEIIDDES-1100 Using Flat File Importer, it doesn't recognize "\n" or "\r\n" in the file
- Closed
-
TEIIDDES-1782 DDL import wizard - add better control over selection of imported objects
- Closed